yc.o sync (#1584)

* Cronjob - daily check of IANA modules. * Cronjob - daily check of IETF modules. --------- Co-authored-by: Miroslav Kovac <mirkovac@cisco.com>
YangModels · Sep 19, 2024 · 4e2cc4a · 4e2cc4a
1 parent de91d44
commit 4e2cc4a
Show file tree

Hide file tree

Showing 6 changed files with 1,247 additions and 102 deletions.
diff --git a/experimental/ietf-extracted-YANG-modules/ietf-ac-svc@2024-08-06.yang b/experimental/ietf-extracted-YANG-modules/ietf-ac-svc@2024-08-06.yang
@@ -81,7 +81,6 @@ module ietf-ac-svc {
       "Defines a reference to an attachment circuit that can be used
        by other modules.";
   }
-
   typedef ac-group-reference {
     type leafref {
       path "/ac-svc:attachment-circuits/ac-svc:ac-group-profile"
@@ -562,7 +561,6 @@ module ietf-ac-svc {
     uses ac-common:ospf-authentication;
     uses ac-common:service-status;
   }
-
   //  IS-IS Service
 
   grouping isis-svc {
@@ -803,7 +801,6 @@ module ietf-ac-svc {
   }
 
   // Encryption choice
-
   grouping encryption-choice {
     description
       "Container for the encryption profile.";

diff --git a/...s/ietf-adapt-subscription@2024-06-13.yang → ...s/ietf-adapt-subscription@2024-09-09.yang b/...s/ietf-adapt-subscription@2024-06-13.yang → ...s/ietf-adapt-subscription@2024-09-09.yang
@@ -19,6 +19,18 @@ module ietf-adapt-subscription {
     reference
       "RFC YYYY: Common YANG Data Types";
   }
+  import ietf-system-capabilities {
+    prefix sysc;
+    reference
+      "RFC 9196: YANG Modules Describing Capabilities for
+       Systems and Datastore Update Notifications";
+  }
+  import ietf-notification-capabilities {
+    prefix notc;
+    reference
+      "RFC 9196: YANG Modules Describing Capabilities for
+       Systems and Datastore Update Notifications";
+  }
 
   organization
     "IETF NETCONF (Network Configuration) Working Group";
@@ -60,8 +72,8 @@ module ietf-adapt-subscription {
      Legal Provisions Relating to IETF Documents
      (https://trustee.ietf.org/license-info).
 
-     This version of this YANG module is part of RFC xxxx
-     (https://www.rfc-editor.org/info/rfcxxxx); see the RFC
+     This version of this YANG module is part of RFC XXXX
+     (https://www.rfc-editor.org/info/rfcXXXX); see the RFC
      itself for full legal notices.
 
      The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
@@ -71,11 +83,17 @@ module ietf-adapt-subscription {
      (RFC 8174) when, and only when, they appear in all
      capitals, as shown here.";
 
-  revision 2024-06-13 {
+  revision 2024-09-09 {
     description
       "Initial revision";
     reference
-      "RFC xxxx: Adaptive Subscription to YANG Notification.";
+      "RFC XXXX: Adaptive Subscription to YANG Notification.";
+  }
+
+  feature adaptive-subscription {
+    description
+      "This feature indicates that adaptive-subscriptions are
+       supported.";
   }
 
   identity adaptive-unsupported {
@@ -161,6 +179,7 @@ module ietf-adapt-subscription {
       "This augmentation adds additional subscription parameters
        that apply specifically to adaptive subscription.";
     case adaptive-periodic {
+      if-feature adaptive-subscription;
       description
         "Defines adaptively periodic case for sending an event
          record to the subscriber.";
@@ -175,6 +194,7 @@ module ietf-adapt-subscription {
        parameters that apply specifically to datastore updates to
        RPC input.";
     case adaptive-periodic {
+      if-feature adaptive-subscription;
       description
         "Defines adaptively periodic case for sending an event
          record to the subscriber.";
@@ -188,6 +208,7 @@ module ietf-adapt-subscription {
        parameters that apply specifically to datastore updates to
        RPC input.";
     case adaptive-periodic {
+      if-feature adaptive-subscription;
       description
         "Defines adaptively periodic case for sending an event
          record to the subscriber.";
@@ -201,6 +222,7 @@ module ietf-adapt-subscription {
        parameters to the notification that a subscription has
        started.";
     case adaptive-periodic {
+      if-feature adaptive-subscription;
       description
         "Defines adaptively periodic case for sending an event
          record to the subscriber.";
@@ -214,6 +236,7 @@ module ietf-adapt-subscription {
        parameters to the notification that a subscription has been
        modified.";
     case adaptive-periodic {
+      if-feature adaptive-subscription;
       description
         "Defines adaptively periodic case for sending an event
          record to the subscriber.";
@@ -222,6 +245,7 @@ module ietf-adapt-subscription {
   }
 
   notification adaptive-period-update {
+    if-feature adaptive-subscription;
     sn:subscription-state-notification;
     description
       "This notification contains a push update that in turn
@@ -264,4 +288,60 @@ module ietf-adapt-subscription {
       }
     }
   }
+
+  grouping adaptive-subscription-capabilities {
+    description
+      "Capabilities related to adaptive subscription and
+       notification.";
+    typedef notification-support {
+      type bits {
+        bit config-changes {
+          description
+            "The publisher is capable of sending
+             notifications for 'config true' nodes for the
+             relevant scope and subscription type.";
+          }
+        bit state-changes {
+          description
+            "The publisher is capable of sending
+             notifications for 'config false' nodes for the
+             relevant scope and subscription type.";
+        }
+      }
+      description
+        "Type for defining whether 'on-change' or
+         'periodic' notifications are supported for all data nodes,
+         'config false' data nodes, 'config true' data nodes, or
+         no data nodes.
+
+         The bits config-changes or state-changes have no effect
+         when they are set for a datastore or for a set of nodes
+         that does not contain nodes with the indicated config
+         value.  In those cases, the effect is the same as if no
+         support was declared.  One example of this is indicating
+         support for state-changes for a candidate datastore that
+         has no effect.";
+    }
+    leaf adaptive-notifications-supported {
+      type notification-support;
+      description
+        "Specifies whether the publisher is capable of sending
+         'adaptive' notifications for the selected data nodes,
+         including any subtrees that may exist below them.";
+    }
+  }
+
+  augment
+    "/sysc:system-capabilities/notc:subscription-capabilities" {
+    description
+      "Add system level capabilities of adaptive subscription.";
+    uses adaptive-subscription-capabilities;
+  }
+
+  augment "/sysc:system-capabilities/sysc:datastore-capabilities/"
+     + "sysc:per-node-capabilities/notc:subscription-capabilities" {
+    description
+      "Add node-level capabilities of adaptive subscription.";
+    uses adaptive-subscription-capabilities;
+  }
 }