Cronjob - daily update of yang files.

experimental/ietf-extracted-YANG-modules/ietf-ace-brski-ace@2023-07-07.yang

@@ -0,0 +1,81 @@
+module ietf-ace-brski-ace {
+  yang-version 1.1;
+
+  namespace "urn:ietf:params:xml:ns:yang:ietf-ace-brski-ace";
+
+  prefix vch-ace;
+
+  import ietf-voucher {
+    prefix vch;
+    reference "I-D.ietf-anima-rfc8366bis-07";
+  }
+
+  organization
+    "IETF ACE (Authentication and Authorization for Constrained Environments)
+    Working Group";
+
+  contact
+    "WG Web:   <http://tools.ietf.org/wg/ace/>
+     WG List:  <mailto:[email protected]>
+
+     Editor:   Christian Amsüss
+               <mailto:[email protected]>";
+
+  description
+    "This module augments the voucher artifact for bootstrapping
+    (onboarding) with mechanisms for onboarding onto ACE (Authentication
+    and Authorization for Constrained Environments) Authorization
+    Servers.
+
+    Copyright (c) 2019 IETF Trust and the persons identified as
+    authors of the code. All rights reserved.
+
+    Redistribution and use in source and binary forms, with or
+    without modification, is permitted pursuant to, and subject
+    to the license terms contained in, the Simplified BSD License
+    set forth in Section 4.c of the IETF Trust's Legal Provisions
+    Relating to IETF Documents
+    (http://trustee.ietf.org/license-info).
+
+    This version of this YANG module is part of RFC XXXX; see the
+    RFC itself for full legal notices.";
+
+  revision 2023-07-07 {
+    description
+      "Initial revision.";
+
+    reference
+      "I-D.amsuess-ace-brski-ace, Provisioning ACE credentials through
+      BRSKI";
+  }
+
+  uses "vch:voucher-artifact-grouping" {
+    augment "voucher" {
+      description
+        "Mechanisms for onboarding onto ACE (Authentication and Authorization
+        for Constrained Environments) Authorization Servers";
+
+      leaf ace-as-key {
+        type binary;
+        description
+          "Key(s) held by the ACE Authorization Server by which it
+          authenticates (and the Resource Server verifies) tokens.
+          It is a CBOR encoded COSE_KeySet.";
+        reference
+          "I-D.amsuess-ace-brski-ace, Provisioning ACE credentials
+          through BRSKI";
+      }
+
+      leaf ace-aud {
+        type string;
+        description
+          "Audience identifier by which the ACE Authorization Server
+          will be the pledge that is enrolled as an ACE Resource
+          Server.";
+        reference
+          "I-D.amsuess-ace-brski-ace, Provisioning ACE credentials
+          through BRSKI";
+      }
+    }
+  }
+}

experimental/ietf-extracted-YANG-modules/ietf-computing-information@2022-05-11.yang

@@ -0,0 +1,124 @@
+module ietf-computing-information {
+  yang-version "1.1";
+  namespace "urn:ietf:params:xml:ns:yang: ietf-computing-information";
+
+  prefix computing-information;
+
+  import ietf-inet-types {
+    prefix inet ;
+    revision-date 2013-07-15 ;
+    reference "RFC 6991: Common YANG Data Types";
+  }
+
+  organization
+    "IETF cats(Computing-Aware Traffic Steering)Working Group";
+
+  contact
+    "WG Web:   <http://datatracker.ietf.org/group/cats/>
+     WG List:  <mailto:[email protected]>
+
+     Author:   Xuewei Wang
+               <mailto:[email protected]>
+     Author:   Huijuan Yao
+               <mailto:[email protected]>
+     Author:   Zhiqiang Li
+               <mailto:[email protected]> ";
+
+  description
+    "This document defines a YANG data model used for computing information awareness.
+
+     Copyright (c) 2023 IETF Trust and the persons identified as
+     authors of the code.  All rights reserved.
+
+     Redistribution and use in source and binary forms, with or
+     without modification, is permitted pursuant to, and subject to
+     the license terms contained in, the Revised BSD License set
+     forth in Section 4.c of the IETF Trust's Legal Provisions
+     Relating to IETF Documents
+     (https://trustee.ietf.org/license-info).
+
+     This version of this YANG module is part of RFC XXXX;
+     see the RFC itself for full legal notices.
+
+     The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
+     NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
+     'MAY', and 'OPTIONAL' in this document are to be interpreted as
+     described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
+     they appear in all capitals, as shown here.";
+
+  revision 2022-05-11 {
+    description 'First draft.'
+                ;
+    reference 'RFC XXXX: A YANG Data Model for Computing '
+            + 'Information Awareness.'
+                ;
+  }
+
+  container awareness {
+    description 'transferring of computing information of the service.'
+                ;
+    container computing-information {
+      description 'computing information transferring.'
+                  ;
+      container service-instance {
+        description 'computing information of a service instance.'
+                    ;
+           leaf service-ID {
+             type inet:ip-prefix;
+             description ' The ID of the service provided by the service instance '
+                         ;
+           }
+           leaf service-domain-name {
+             type string;
+             description ' The domain name of the service provided by the service instance '
+                         ;
+           }
+           leaf computing-energy-consumption {
+             type uint32
+             description ' the value of computing energy consumption '
+                         ;
+           }
+           leaf computing-cost {
+             type uint32
+             description ' the comprehensive computing cost '
+                         ;
+           }
+           leaf peak-value-of-available-computing {
+             type uint32
+             description ' the peak value of available computing '
+                         ;
+           }
+           leaf number-of-available-service-connections {
+             type uint32
+             description ' the number of available service connections '
+                         ;
+           }
+           leaf CPU-performance {
+             type uint16;
+             description ' the CPU utilization'
+                         ;
+           }
+           leaf GPU-performance {
+             type uint16;
+             description ' the GPU utilization'
+                         ;
+           }
+           leaf NPU-performance {
+             type uint16;
+             description ' the NPU utilization'
+                         ;
+           }
+           leaf storage-capacity {
+             type uint32;
+             description ' The capacity of the storage '
+                         ;
+           }
+           leaf service-delay {
+             type uint32;
+             description ' Service processing latency '
+                         ;
+        }
+      }
+    }
+  }
+}

experimental/ietf-extracted-YANG-modules/ietf-incident-types@2023-05-16.yang

@@ -0,0 +1,156 @@
+module ietf-incident-types {
+  yang-version "1.1";
+  namespace "urn:ietf:params:xml:ns:yang:ietf-incident-types";
+  prefix "int";
+
+  import ietf-network {
+    prefix nw;
+    reference
+      "RFC 8345: A YANG Data Model for Network Topologies";
+  }
+
+  organization
+    "IETF OPSAWG Working Group";
+  contact
+    "WG Web:   <https://datatracker.ietf.org/wg/opsawg/>;
+     WG List:  <mailto:[email protected]>
+     Author:   Chong Feng  <mailto:[email protected]>
+     Author:   Tong Hu  <mailto:[email protected]>
+     Author:   Luis Miguel Contreras Murillo <mailto:
+               [email protected]>
+     Author :  Thomas Graf   <mailto:[email protected]>
+     Author :  Qin Wu   <mailto:[email protected]>
+     Author:   Chaode Yu   <mailto:[email protected]>
+     Author:   Nigel Davis   <mailto:[email protected]>";
+
+  description
+    "This module defines the identities and typedefs for
+     incident management.
+
+     Copyright (c) 2022 IETF Trust and the persons identified as
+     authors of the code.  All rights reserved.
+
+     Redistribution and use in source and binary forms, with or
+     without modification, is permitted pursuant to, and subject
+     to the license terms contained in, the Revised BSD License
+     set forth in Section 4.c of the IETF Trust's Legal Provisions
+     Relating to IETF Documents
+     (https://trustee.ietf.org/license-info).
+     This version of this YANG module is part of RFC XXXX; see the
+     RFC itself for full legal notices.  ";
+  revision 2023-05-16 {
+    description "initial version";
+    reference "RFC XXX: Yang module for incident management.";
+  }
+  //identities
+  identity incident-domain {
+    description "The abstract identity to indicate the domain of
+                 an incident.";
+  }
+  identity single-domain {
+    base incident-domain;
+    description "single domain.";
+  }
+  identity access {
+    base single-domain;
+    description "access domain.";
+  }
+  identity ran {
+    base access;
+    description "radio access network domain.";
+  }
+  identity transport {
+    base single-domain;
+    description "transport domain.";
+  }
+  identity otn {
+    base transport;
+    description "optical transport network domain.";
+  }
+  identity ip {
+    base single-domain;
+    description "ip domain.";
+  }
+  identity ptn {
+    base ip;
+    description "packet transport network domain.";
+  }
+
+  identity cross-domain {
+    base incident-domain;
+    description "cross domain.";
+  }
+  identity incident-category {
+    description "The abstract identity for incident category.";
+  }
+  identity device {
+    base incident-category;
+    description "device category.";
+  }
+  identity power-enviorment {
+    base device;
+    description "power system category.";
+  }
+  identity device-hardware {
+    base device;
+    description "hardware of device category.";
+  }
+  identity device-software {
+    base device;
+    description "software of device category";
+  }
+  identity line {
+    base device-hardware;
+    description "line card category.";
+  }
+  identity maintenance {
+    base incident-category;
+    description "maintenance category.";
+  }
+  identity network {
+    base incident-category;
+    description "network category.";
+  }
+  identity protocol {
+    base incident-category;
+    description "protocol category.";
+  }
+  identity overlay {
+    base incident-category;
+    description "overlay category";
+  }
+  identity vm {
+    base incident-category;
+    description "vm category.";
+  }
+
+  //typedefs
+  typedef incident-priority {
+    type enumeration {
+      enum critical {
+        description "the incident MUST be handled immediately.";
+      }
+      enum high {
+        description "the incident should be handled as soon as
+                     possible.";
+      }
+      enum medium {
+        description "network services are not affected, or the
+                     services are slightly affected,but corrective
+                     measures need to be taken.";
+      }
+      enum low {
+        description "potential or imminent service-affecting
+                     incidents are detected,but services are
+                     not affected currently.";
+      }
+    }
+    description "define the priority of incident.";
+  }
+  typedef node-ref {
+    type leafref {
+      path "/nw:networks/nw:network/nw:node/nw:node-id";
+    }
+    description "reference a network node.";
+  }
+}