exempt annotation

romeyod · Sep 19, 2024 · d4f9259 · d4f9259
1 parent 716ee62
commit d4f9259
Showing 1 changed file with 22 additions and 1 deletion.
diff --git a/release/models/openconfig-extensions.yang b/release/models/openconfig-extensions.yang
@@ -20,6 +20,12 @@ module openconfig-extensions {
 
   oc-ext:openconfig-version "0.5.1";
 
+  revision "2024-09-19" {
+    description
+      "Add telemetry-atomic-exempt annotation.";
+    reference "0.5.2";
+  }
+
   revision "2022-10-05" {
     description
       "Add missing version statement.";
@@ -154,7 +160,7 @@ module openconfig-extensions {
   extension telemetry-atomic {
     description
       "The telemetry-atomic annotation is specified in the context of
-      a subtree (containre, or list), and indicates that all nodes
+      a subtree (container, or list), and indicates that all nodes
       within the subtree are always updated together within the data
       model. For example, all elements under the subtree may be updated
       as a result of a new alarm being raised, or the arrival of a new
@@ -164,6 +170,21 @@ module openconfig-extensions {
       optimisations for sending or storing the corresponding data.";
   }
 
+  extension telemetry-atomic-exempt {
+    description
+      "The telemetry-atomic-exempt annotation is specified in the context
+      of a subtree (container, or list), and indicates that all nodes
+      within the subtree are not always updated together within the data
+      model of the parent tree. All elements under the
+      subtree may not be updated as a result of a new alarm being raised,
+      or the arrival of a new protocol message that updates the parent
+      tree.
+
+      This annotation allows parent tree containers with telemetry-atomic
+      annotation  to not be updated when a more frequently updated subtree
+      (like a counters container) is present.";
+  }
+
   extension operational {
     description
       "The operational annotation is specified in the context of a