diff --git a/experimental/ietf-extracted-YANG-modules/ietf-altmark@2026-01-02.yang b/experimental/ietf-extracted-YANG-modules/ietf-altmark@2026-06-11.yang similarity index 51% rename from experimental/ietf-extracted-YANG-modules/ietf-altmark@2026-01-02.yang rename to experimental/ietf-extracted-YANG-modules/ietf-altmark@2026-06-11.yang index 0d5ee43e5..a1586095c 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-altmark@2026-01-02.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-altmark@2026-06-11.yang @@ -16,14 +16,6 @@ module ietf-altmark { "RFC 8343: A YANG Data Model for Interface Management"; } - import ietf-lime-time-types { - prefix "lime"; - reference - "RFC 8532: Generic YANG Data Model for the Management of - Operations, Administration, and Maintenance (OAM) Protocols - That Use Connectionless Communications"; - } - organization "IETF IPPM (IP Performance Metrics) Working Group"; @@ -39,13 +31,14 @@ module ietf-altmark { description "This YANG module specifies a vendor-independent data model for the Alternate Marking (AltMark). + 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. - Copyright (c) 2024 IETF Trust and the persons identified as + Copyright (c) 2026 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or @@ -59,7 +52,7 @@ module ietf-altmark { (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself for full legal notices."; - revision 2026-01-02 { + revision 2026-06-11 { description "First revision."; reference "RFC XXXX: A YANG Data Model for Alternate-Marking"; } @@ -68,14 +61,18 @@ module ietf-altmark { * FEATURES */ - feature altmark - { + feature altmark { description "This feature indicated that the Alternate-Marking Method is supported."; reference "RFC 9341: Alternate-Marking Method; - RFC 9342: Clustered Alternate-Marking Method"; + RFC 9342: Clustered Alternate-Marking Method + RFC 9343: IPv6 Application of the Alternate-Marking Method + RFC 9714: Application of the Alternate Marking Method to the + MPLS Label Stack + RFC 9947: Application of the Alternate Marking Method to the + Segment Routing Header"; } /* @@ -87,6 +84,7 @@ module ietf-altmark { "Base identity to represent a filter. A filter is used to specify the flow to which the AltMark method is applied."; } + identity acl-filter { base filter; description @@ -125,16 +123,16 @@ module ietf-altmark { "RFC 9343: IPv6 Application of the Alternate-Marking Method"; } - identity srh { + identity srh { base protocol; description "The AltMark method is applied to SRH."; reference - "[I-D.fz-spring-srv6-alt-mark]: Application of the - Alternate Marking Method to the Segment Routing Header"; + "RFC 9947: Application of the Alternate Marking Method to the + Segment Routing Header"; } - identity mpls { + identity mpls { base protocol; description "The AltMark method is applied to MPLS."; @@ -143,73 +141,36 @@ module ietf-altmark { to the MPLS Label Stack"; } - identity node-action { + identity interface-action { description - "Base identity to represent the node actions. It's used to - indicate what action the node will take."; + "Base identity to represent the interface actions. It's used to + indicate what action the node will take on that interface."; } identity action-marking { - base node-action; + base interface-action; description - "It indicates that the node must mark the AltMark data field, - according to the operations described in RFC 9341 and + "It indicates that the interface must mark the AltMark data + field, according to the operations described in RFC 9341 and RFC 9342"; } identity action-unmarking { - base node-action; + base interface-action; description - "It indicates that the node must unmark the AltMark data field, - according to the operations described in RFC 9341 and - RFC 9342"; + "It indicates that the interface must unmark the AltMark data + field, according to the operations described in RFC 9341 and + RFC 9342"; } identity action-read { - base node-action; - description - "It indicates the node only reads the AltMark data, - according to the operations described in RFC 9341 and - RFC 9342"; - } - - identity measurement-period { - description - "It indicates the AltMark Period."; - } - - identity flow-mon-id { - description - "It indicates the FlowMonID."; - } - - identity measurement-mode { + base interface-action; description - "It indicates the measurement mode."; + "It indicates that the interface only reads the AltMark data, + according to the operations described in RFC 9341 and + RFC 9342"; } - identity hbh-measurement { - base measurement-mode; - description - "It indicates that hop-by-hop measurements can be enabled."; - } - - identity e2e-measurement { - base measurement-mode; - description - "It indicates that end-to-end measurements can be enabled."; - } - - identity enable-loss-measurement { - description - "It indicates that loss measurements are enabled."; - } - - identity enable-delay-measurement { - description - "It indicates that delay measurements are enabled."; - } - /* * TYPE DEFINITIONS */ @@ -222,12 +183,12 @@ module ietf-altmark { "It specifies a known type of filter."; } - typedef altmark-node-action { + typedef altmark-interface-action { type identityref { - base node-action; + base interface-action; } description - "It specifies a node action."; + "It specifies the action on the interface."; } typedef altmark-method-type { @@ -247,9 +208,47 @@ module ietf-altmark { data."; } + typedef flow-id { + type uint32 { + range 0..1048575; + } + description + "It specifies the 20-bit AltMark flow identifier."; + } + + typedef flow-direction { + type enumeration { + enum "ingress" { + value 1; + description + "Ingress of an AltMark flow."; + } + enum "transit" { + value 2; + description + "Transit of an AltMark flow."; + } + enum "egress" { + value 3; + description + "Egress of an AltMark flow."; + } + } + description + "Flow direction."; + } typedef altmark-measurement-mode { - type identityref { - base measurement-mode; + type enumeration { + enum "e2e" { + value 1; + description + "It indicates that end-to-end measurements can be enabled."; + } + enum "hbh" { + value 2; + description + "It indicates that hop-by-hop measurements can be enabled."; + } } description "It specifies the measurement mode."; @@ -259,8 +258,24 @@ module ietf-altmark { * GROUP DEFINITIONS */ + grouping altmark-admin-config { + description + "AltMark top-level administrative configuration."; + + leaf enabled { + type boolean; + default false; + description + "This object is to control the availability of configuration. + It MUST be true before anything in the + /altmark/altmark-profile can be edited. + If false, any configuration in place is not used."; + } + } + grouping altmark-filter { - description "A grouping for AltMark filter definition"; + description + "A grouping for AltMark filter definition"; leaf filter-type { type altmark-filter-type; @@ -273,29 +288,9 @@ module ietf-altmark { type leafref { path "/acl:acls/acl:acl/acl:aces/acl:ace/acl:name"; } - description "The Access Control Entry name is used to - refer to an ACL specification."; - } - } - - grouping measurement-mode { - description - "A grouping for measurement mode."; - - leaf hbh-measurement { - type boolean; - default false; - description - "This object indicates that hop-by-hop measurements can be - enabled."; - } - - leaf e2e-measurement { - type boolean; - default false; description - "This object indicates that end-to-end measurements can be - enabled."; + "The Access Control Entry name is used to refer to an + ACL specification."; } } @@ -303,49 +298,37 @@ module ietf-altmark { description "A grouping for AltMark profile."; - leaf node-action { - type altmark-node-action; - default action-read; + leaf flow-mon-id { + type flow-id; description - "This object indicates the action that the node needs to - take, i.e. marking/read/unmarking."; + "It specifies the FlowMonID. A 20-bit flow identifier as + defined in RFC 9343 and RFC 9714. The field is set at the + marking node. The FlowMonID can be uniformly assigned by + a central controller or algorithmically generated by the + marking node. Note that it corresponds to the + altmarkFlowMonID parameter defined in + draft-ietf-opsawg-ipfix-alt-mark."; } - leaf measurement-period { - type uint64; + leaf method-type { + type altmark-method-type; description - "It specifies the AltMark marking period."; + "This item is used to indicate the AltMark method."; } - leaf flow-mon-id { - type uint32; + leaf measurement-period { + type uint64; description - "It specifies the FlowMonID. - A 20-bit flow identifier. The field is set at the marking node. - The FlowMonID can be uniformly assigned by a central controller - or algorithmically generated by the marking node. - The latter approach cannot guarantee the uniqueness of the - FlowMonID, yet the conflict probability is small due to the - large space. - FlowMonID is used to identify the flow and to correlate the - exported data of the same flow from multiple nodes and from - multiple packets."; + "It specifies the AltMark marking period. Its value can be set + according to RFC 9341, RFC 9342 and + draft-ietf-ippm-alt-mark-deployment"; } - } - - grouping altmark-admin-config { - description - "AltMark top-level administrative configuration."; - - leaf enabled { - type boolean; - default false; + leaf measurement-mode { + type altmark-measurement-mode; + default "hbh"; description - "This object is to control the availability of configuration. - It MUST be true before anything in the - /altmark/altmark-profile can be edited. - If false, any configuration in place is not used."; + "It specifies the AltMark measurement mode."; } } @@ -353,103 +336,101 @@ module ietf-altmark { * DATA NODES */ - container AltMark { - description "AltMark top level container"; + container altmark { + description + "AltMark top level container"; - container altmark-info { - config false; + container admin-config { description - "Describes information such as units or timestamp format - that assists monitoring systems in the interpretation of the - AltMark data."; + "Contains all the administrative configurations related to + the AltMark functionalities"; - leaf timestamp-type { - type identityref { - base lime:timestamp-type; - } - description - "Type of timestamp, such as Truncated PTP or NTP."; - } + uses altmark-admin-config; + } + container available-interfaces { + description + "It contains the list of the interfaces to be activated for + AltMark"; list available-interface { key "if-name"; description "A list of available interfaces that support - Alternate-Marking."; + Alternate-Marking."; leaf if-name { type if:interface-ref; description "This is a reference to the Interface name."; } - } - } - - container altmark-profiles { - description - "Contains the AltMark profiles."; - - container admin-config { - description - "Contains all the administrative configurations related to - the AltMark functionalities"; - - uses altmark-admin-config; - } - - list altmark-profile { - if-feature altmark; - key "profile-name"; - description - "It describes the list of the AltMark profiles configured - on the node"; - leaf profile-name { - type string{ - length "1..300"; - } - description - "Unique identifier for each AltMark profile."; - } - container filter { - uses altmark-filter; + container altmark-profiles { description - "The filter which is used to indicate the flow where - the AltMark is applied."; - } - - leaf method-type { - type altmark-method-type; - description - "This item is used to indicate the AltMark method."; - } - - leaf protocol-type { - type altmark-protocol-type; - description - "This item is used to indicate the carrier protocol where - the AltMark is applied."; - } - - uses altmark-setup; + "Contains the AltMark profiles."; - uses measurement-mode; - - leaf enable-loss-measurement { - type boolean; - default false; - description - "If true, it indicates that loss measurements are - enabled."; - } - - leaf enable-delay-measurement { - type boolean; - default false; + list altmark-profile { + if-feature altmark; + key "altmark-profile-name"; description - "If true, it indicates that delay measurements are - enabled."; + "It describes the list of the AltMark profiles + configured on the node. The AltMark feature MUST be + enabled on the node before anything in the + altmark-profile can be edited"; + + leaf altmark-profile-name { + type string{ + length "1..300"; + } + description + "Unique identifier for each AltMark profile."; + } + + container filter { + uses altmark-filter; + description + "The filter which is used to indicate the flow where + the AltMark is applied."; + } + + leaf direction { + type flow-direction; + description + "Specify the flow direction."; + } + + leaf interface-action { + type altmark-interface-action; + default action-read; + description + "This object indicates the action that the node needs + to take, i.e. marking/read/unmarking."; + } + + leaf protocol-type { + type altmark-protocol-type; + description + "This item is used to indicate the carrier protocol + where the AltMark is applied."; + } + + uses altmark-setup; + + leaf enable-loss-measurement { + type boolean; + default false; + description + "If true, it indicates that loss measurements are + enabled."; + } + + leaf enable-delay-measurement { + type boolean; + default false; + description + "If true, it indicates that delay measurements are + enabled."; + } } - + } } - } } + } } diff --git a/experimental/ietf-extracted-YANG-modules/ietf-cmis-control-action@2026-05-12.yang b/experimental/ietf-extracted-YANG-modules/ietf-cmis-control-action@2026-05-12.yang index 85d5e3b0d..10319a3c6 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-cmis-control-action@2026-05-12.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-cmis-control-action@2026-05-12.yang @@ -11,7 +11,7 @@ module ietf-cmis-control-action { "IETF CCAMP Working Group"; contact - "WG Web: + "WG Web: WG List: Editor: Shunsuke Homma @@ -115,10 +115,11 @@ module ietf-cmis-control-action { "Write CMIS register data via action context. The operation MUST respect the governance policy defined in the 'cmis-control' container of the target interface. - If the target page is not in the 'remote-write-allowed-pages' - list, the server MUST reject the request. - Writing to Lower Memory (Address 0-127) MUST NOT be performed - to prevent interference with Host management."; + If the target page is not in the + 'remote-write-allowed-pages' list, the server MUST + reject the request. Writing to Lower Memory + (Address 0-127) MUST NOT be performed to prevent + interference with Host management."; input { leaf page { type uint8; @@ -153,7 +154,7 @@ module ietf-cmis-control-action { governance policy (e.g., page not in whitelist)."; } enum io-error { - description "I/O error during write"; + description "I/O error during write."; } enum invalid-params { description "Bad parameters"; @@ -161,13 +162,15 @@ module ietf-cmis-control-action { } description "Result of the write operation."; } + leaf post-write-value { type binary; description "Optional read-back of the target value after write. Present only if the implementation performed a read-back - (e.g., for 'rw' registers). Not present for 'wo' registers - or when no-readback was requested/possible."; + (e.g., for 'rw' registers). Not present for 'wo' + registers or when no-readback was + requested/possible."; } } } diff --git a/experimental/ietf-extracted-YANG-modules/ietf-cmis-control-primitive@2025-04-21.yang b/experimental/ietf-extracted-YANG-modules/ietf-cmis-control-primitive@2025-04-21.yang deleted file mode 100644 index b726fc935..000000000 --- a/experimental/ietf-extracted-YANG-modules/ietf-cmis-control-primitive@2025-04-21.yang +++ /dev/null @@ -1,121 +0,0 @@ -module ietf-cmis-control-primitive { - yang-version 1.1; - namespace "urn:ietf:params:xml:ns:yang:ietf-cmis-control-primitive"; - prefix cmis-ctrl-pm; - - import ietf-interfaces { - prefix if; - } - - organization - "IETF CCAMP Working Group"; - - contact - "WG Web: - WG List: - - Editor: Shunsuke Homma - - - Editor: Hitoshi Irino - "; - - description - "This YANG module defines a data model for the management - of CMIS (Common Management Interface Specification) pages - as specified by OIF with RPC. It enables configuration and - retrieval of CMIS page data, including access types and - value fields, to support the management of pluggable optical - modules via NETCONF or RESTCONF. - - 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. - - Copyright (c) 2025 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 - (http://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 itself - for full legal notices."; - -// RFC Ed.: replace XXXX with actual RFC number and remove this note - - revision "2025-04-21" { - description - "Initial revision."; - reference - "RFC XXXX: A YANG Data Model for CMIS Access and Control"; - } - - augment "/if:interfaces/if:interface" { - description "Add primitive CMIS read/write actions under interface."; - - action cmis-read { - description "Read CMIS register under this interface."; - input { - leaf page { - type uint8; - mandatory true; - description "The number of the CMIS page."; - } - leaf bank { - type uint8; - mandatory true; - description "The bank of the CMIS page."; - } - leaf offset { - type uint8; - mandatory true; - description "The memory address of the value."; - } - leaf size { - type uint8; - default 1; - description "The memory size of the value."; - } - } - output { - leaf data { - type binary; - description "Raw register data."; - } - } - } - - action cmis-write { - description "Write CMIS register under this interface."; - input { - leaf page { - type uint8; - mandatory true; - description "The number of the CMIS page."; - } - leaf bank { - type uint8; - mandatory true; - description "The bank of the CMIS page."; - } - leaf offset { - type uint8; - mandatory true; - description "The memory address of the value."; - } - leaf data { - type binary; - mandatory true; - description "Data to write."; - } - } - } - } -} diff --git a/experimental/ietf-extracted-YANG-modules/ietf-cmis-control-primitive@2026-06-10.yang b/experimental/ietf-extracted-YANG-modules/ietf-cmis-control-primitive@2026-06-10.yang new file mode 100644 index 000000000..b0382a0da --- /dev/null +++ b/experimental/ietf-extracted-YANG-modules/ietf-cmis-control-primitive@2026-06-10.yang @@ -0,0 +1,154 @@ +module ietf-cmis-control-primitive { + yang-version 1.1; + namespace + "urn:ietf:params:xml:ns:yang:ietf-cmis-control-primitive"; + prefix cmis-ctrl-pm; + + import ietf-interfaces { + prefix if; + } + + organization + "IETF CCAMP Working Group"; + + contact + "WG Web: + WG List: + + Editor: Shunsuke Homma + + + Editor: Hitoshi Irino + "; + + description + "This YANG module defines a primitive data model for the + management of CMIS (Common Management Interface Specification) + pages as specified by OIF. It treats CMIS page memory as a + flat data structure without supplemental information such as + access types or descriptions, to support the management of + pluggable optical modules via NETCONF or RESTCONF. + + Copyright (c) 2026 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 + (http://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 itself + for full legal notices."; + +// RFC Ed.: replace XXXX with actual RFC number and remove this note + + revision "2026-06-10" { + description + "Restored the datastore-based module definition; the module + body in the previous revisions of this document had been + erroneously replaced with action definitions."; + reference + "I-D.hi-ccamp-cmis-control-yang-03"; + } + + revision "2025-04-21" { + description + "Initial revision."; + reference + "I-D.hi-ccamp-cmis-control-yang-00"; + } + + /* + * Primitive Mode of CMIS control data nodes + */ + + grouping primitive-cmis-page { + description + "Parameters stored in the CMIS page as flat data structure"; + + leaf page-num { + type uint8 { + range "0 .. 255"; + } + description + "The number of the CMIS page."; + } + + leaf bank { + type uint8; + mandatory true; + description + "The banks corresponding to the CMIS page."; + } + + leaf offset { + type uint8; + mandatory true; + description + "The memory address of the value."; + } + + leaf size { + type uint8 { + range "1 .. 128"; + } + mandatory true; + description + "The memory size of the value."; + } + + leaf value { + type binary; + mandatory true; + description + "The actual data to write to the CMIS memory."; + } + } + + grouping cmis-control-primitive { + description + "Parameters for primitive CMIS control of the pluggable + device equipped in the interface."; + + leaf cmis-enabled { + type boolean; + default "false"; + config false; + description + "The availability of the CMIS for control the pluggable + device equipped in the interface. If the device does not + support CMIS, this value is false."; + } + + leaf cmis-version { + type string; + config false; + description + "The version of the CMIS by the pluggable device."; + } + + list primitive-cmis-page { + key "page-num"; + description + "A flat representation of CMIS page memory."; + uses primitive-cmis-page; + } + } + + /* + * Augment Interface + */ + + augment "/if:interfaces/if:interface" { + description + "Augments interface with primitive CMIS control parameters."; + container cmis-control-primitive { + description + "Container for primitive CMIS control."; + uses cmis-control-primitive; + } + } +} diff --git a/experimental/ietf-extracted-YANG-modules/ietf-cmis-control-rpc@2026-05-12.yang b/experimental/ietf-extracted-YANG-modules/ietf-cmis-control-rpc@2026-05-12.yang index 8d4176d2e..901330676 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-cmis-control-rpc@2026-05-12.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-cmis-control-rpc@2026-05-12.yang @@ -11,7 +11,7 @@ module ietf-cmis-control-rpc { "IETF CCAMP Working Group"; contact - "WG Web: + "WG Web: WG List: Editor: Shunsuke Homma @@ -115,10 +115,11 @@ module ietf-cmis-control-rpc { "Write CMIS register data to a pluggable module. The operation MUST respect the governance policy defined in the 'cmis-control' container of the target interface. - If the target page is not in the 'remote-write-allowed-pages' - list, the server MUST reject the request. - Writing to Lower Memory (Address 0-127) MUST NOT be performed - to prevent interference with Host management."; + If the target page is not in the + 'remote-write-allowed-pages' list, the server MUST + reject the request. Writing to Lower Memory + (Address 0-127) MUST NOT be performed to prevent + interference with Host management."; input { leaf interface-name { type leafref{ diff --git a/experimental/ietf-extracted-YANG-modules/ietf-cmis-control@2026-05-12.yang b/experimental/ietf-extracted-YANG-modules/ietf-cmis-control@2026-05-12.yang index b480ad2cb..b61cbfc1f 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-cmis-control@2026-05-12.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-cmis-control@2026-05-12.yang @@ -10,7 +10,7 @@ module ietf-cmis-control { organization "IETF CCAMP Working Group"; contact - "WG Web: + "WG Web: WG List: Editor: Shunsuke Homma @@ -88,12 +88,13 @@ module ietf-cmis-control { effect."; } enum ro/cor { - description "A write-only element with celan-on-read side + description "A read-only element with clear-on-read side effect."; } } description - "Defines access types for CMIS elements as defined in OIF-CMIS."; + "Defines access types for CMIS elements as defined in + OIF-CMIS."; } grouping cmis-page { @@ -161,7 +162,7 @@ module ietf-cmis-control { description "The data contained in the value. It is writable only when the access-type is not Read-Only or Read-Only with - clean-on-read side effect."; + clear-on-read side effect."; } leaf description { @@ -226,10 +227,11 @@ module ietf-cmis-control { list remote-read-allowed-pages { key "page-num"; description - "A whitelist of pages that are allowed to be READ by - a remote controller, even if the default-policy is 'disabled'. - This list is useful when 'default-policy' is set to 'disabled' - but specific pages need to be monitored. + "A whitelist of pages that are allowed to be READ + by a remote controller, even if the default-policy + is 'disabled'. This list is useful when + 'default-policy' is set to 'disabled' but specific + pages need to be monitored. Note: Lower Memory (Address 0-127) SHOULD NOT be included in this list if it contains Clear-on-Read (CoR) registers that @@ -253,13 +255,15 @@ module ietf-cmis-control { Note: Lower Memory (Address 0-127) MUST NOT be included in this list as it contains critical Host management flags. - When a page is removed from this list, or when the default-policy - changes to 'disabled' (and the page is not in the read-whitelist), + When a page is removed from this list, or when the + default-policy changes to 'disabled' (and the page is + not in the read-whitelist), the Host NOS MUST strictly enforce its local configuration - (running-config) to the target CMIS pages. - Values modified by a remote controller MUST be overwritten by - the Host's local configuration or reset to default values to - maintain configuration consistency."; + (running-config) on the target CMIS pages. + Values modified by a remote controller MUST be + overwritten by the Host's local configuration or reset + to default values to maintain configuration + consistency."; leaf page-num { type uint8; diff --git a/experimental/ietf-extracted-YANG-modules/ietf-cmis-monitor@2025-10-11.yang b/experimental/ietf-extracted-YANG-modules/ietf-cmis-monitor@2025-10-11.yang index 09f12b4f1..fdb115698 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-cmis-monitor@2025-10-11.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-cmis-monitor@2025-10-11.yang @@ -124,13 +124,17 @@ module ietf-cmis-monitor { type decimal64 { fraction-digits 2; } - description "Threshold value for triggering notification (only used for threshold type)."; + description + "Threshold value for triggering notification + (only used for threshold type)."; } leaf delta-rate { type decimal64 { fraction-digits 2; } - description "Maximum allowed change per interval (only used for delta-rate type)."; + description + "Maximum allowed change per interval (only used for + delta-rate type)."; } } @@ -149,12 +153,13 @@ module ietf-cmis-monitor { } notification cmis-monitor-event { - description "Notification raised when monitor rule condition is met."; - + description + "Notification raised when monitor rule condition is met."; leaf interface-name { type string; description "Interface name of the monitored module."; } + leaf rule-id { type string; description "ID of the rule that triggered this notification."; diff --git a/experimental/ietf-extracted-YANG-modules/ietf-on-path-telemetry@2026-01-02.yang b/experimental/ietf-extracted-YANG-modules/ietf-on-path-telemetry@2026-01-02.yang deleted file mode 100644 index a520acc8e..000000000 --- a/experimental/ietf-extracted-YANG-modules/ietf-on-path-telemetry@2026-01-02.yang +++ /dev/null @@ -1,655 +0,0 @@ -module ietf-on-path-telemetry { - yang-version 1.1; - namespace "urn:ietf:params:xml:ns:yang:ietf-on-path-telemetry"; - prefix "on-path-telemetry"; - - import ietf-access-control-list { - prefix acl; - reference - "RFC 8519: YANG Data Model for Network Access Control - Lists (ACLs)"; - } - - import ietf-interfaces { - prefix if; - reference - "RFC 8343: A YANG Data Model for Interface Management"; - } - - import ietf-yang-types { - prefix yang; - reference - "Section 3 of RFC 6991"; - } - - organization - "IETF IPPM (IP Performance Metrics) Working Group"; - - contact - "WG Web: - WG List: - Author: giuseppe.fioccola@huawei.com - Author: zhoutianran@huawei.com - Author: zhuyq8@chinatelecom.cn - Author: zhangwq@chinatelecom.cn - Author: zhukeyi@huawei.com"; - - description - "This YANG module specifies a vendor-independent data - model for Alternate Marking Telemetry. - - 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. - Copyright (c) 2024 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 - (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself - for full legal notices."; - - revision 2026-01-02 { - description "First revision."; - reference "RFC XXXX: A YANG Data Model for On-path Telemetry"; - } - - /* - * FEATURES - */ - - feature altmark - { - description - "This feature indicated that the Alternate-Marking Method is - supported."; - reference - "RFC 9341: Alternate-Marking Method; - RFC 9342: Clustered Alternate-Marking Method"; - } - - feature pathdelay - { - description - "This feature indicated that the Path Delay is - supported."; - reference - "[I-D.ietf-opsawg-ipfix-on-path-telemetry]"; - } - - feature incremental-trace - { - description - "This feature indicated that the incremental tracing option is - supported."; - reference "RFC 9197: Data Fields for In-situ OAM"; - } - - feature preallocated-trace - { - description - "This feature indicated that the preallocated tracing option is - supported."; - reference "RFC 9197: Data Fields for In-situ OAM"; - } - - feature direct-export - { - description - "This feature indicated that the direct export option is - supported."; - reference "RFC 9326: In-situ OAM Direct Exporting"; - } - - feature proof-of-transit - { - description - "This feature indicated that the proof of transit option is - supported"; - reference "RFC 9197: Data Fields for In-situ OAM"; - } - - feature edge-to-edge - { - description - "This feature indicated that the edge-to-edge option is - supported."; - reference "RFC 9197: Data Fields for In-situ OAM"; - } - - /* - * IDENTITIES - */ - - identity filter { - description - "Base identity to represent a filter. A filter is used to - specify the flow to which the On-Path Telemetry method is applied."; - } - - identity acl-filter { - base filter; - description - "Apply ACL rules to specify the flow."; - } - - identity protocol { - description - "Base identity to represent the protocol. It's used to - indicate the protocol for the application of the On-Path Telemetry - method."; - } - - identity ipv6 { - base protocol; - description - "The On-Path Telemetry method is applied to IPv6 protocol."; - reference - "RFC 9343: IPv6 Application of the Alternate-Marking Method, - RFC 9486: In-situ OAM IPv6 Options"; - } - - identity srh { - base protocol; - description - "The On-Path Telemetry method is applied to SRH."; - reference - "[I-D.fz-spring-srv6-alt-mark]: Application of the - Alternate Marking Method to the Segment Routing Header"; - } - - identity mpls { - base protocol; - description - "The On-Path Telemetry method is applied to MPLS."; - reference - "RFC 9714: Application of the Alternate Marking Method - to the MPLS Label Stack"; - } - - identity nsh { - base protocol; - description - "The described IOAM data is embedded in NSH."; - reference - "RFC 9452: Network Service Header (NSH) - Encapsulation for In-situ OAM (IOAM) Data"; - } - - identity node-action { - description - "Base identity to represent the node actions. It's used to - indicate what action the node will take."; - } - - identity action-marking { - base node-action; - description - "It indicates that the node must mark the AltMark data field, - according to the operations described in RFC 9341 and - RFC 9342"; - } - - identity action-unmarking { - base node-action; - description - "It indicates that the node must unmark the AltMark data field, - according to the operations described in RFC 9341 and - RFC 9342"; - } - - identity action-read { - base node-action; - description - "It indicates the node only reads the AltMark data, - according to the operations described in RFC 9341 and - RFC 9342"; - } - - identity action-encapsulate { - base node-action; - description - "It indicates the node is to encapsulate the IOAM packet"; - } - - identity action-decapsulate { - base node-action; - description - "It indicates the node is to decapsulate the IOAM packet"; - } - - identity action-transit { - base node-action; - description - "It indicates the node is to transit the IOAM packet"; - } - - identity measurement-period { - description - "It indicates the On-Path Telemetry Period."; - } - - identity measurement-period-number { - description - "It indicates the Period Number."; - } - - identity flow-mon-id { - description - "It indicates the FlowMonID."; - } - - identity method { - description - "Base identity to represent the AltMark method type."; - } - - identity trace-data { - description - "Base identity to represent trace data."; - } - - identity pot-data { - description - "Base identity to represent POT data."; - } - - identity e2e-data { - description - "Base identity to represent E2E data."; - } - - identity telemetry-param-type { - description - "Base identity for telemetry param types"; - } - - identity loss-measurement { - base telemetry-param-type; - description - "To specify loss counters according to RFC 9341"; - } - - identity delay-measurement { - base telemetry-param-type; - description - "To specify timestamps for delay according to RFC 9341"; - } - /* - * TYPE DEFINITIONS - */ - - typedef telemetry-filter-type { - type identityref { - base filter; - } - description - "It specifies a known type of filter."; - } - - typedef telemetry-node-action { - type identityref { - base node-action; - } - description - "It specifies a node action."; - } - - typedef telemetry-protocol-type { - type identityref { - base protocol; - } - description - "It specifies a known type of carrier protocol for the On-path - Telemetry data."; - } - - typedef altmark-method-type { - type identityref { - base method; - } - description - "It specifies the AltMark method used."; - } - - typedef ioam-trace-data { - type identityref { - base trace-data; - } - description - "It specifies the trace data."; - } - - typedef ioam-pot-data { - type identityref { - base pot-data; - } - description - "It specifies the pot data."; - } - - typedef ioam-e2e-data { - type identityref { - base e2e-data; - } - description - "It specifies the edge-to-edge data."; - } - - /* - * GROUP DEFINITIONS - */ - - grouping telemetry-filter { - description "A grouping for On-path Telemetry filter definition"; - - leaf filter-type { - type telemetry-filter-type; - description "filter type"; - } - - leaf ace-name { - when "derived-from-or-self(../filter-type, - 'on-path-telemetry:acl-filter')"; - type leafref { - path "/acl:acls/acl:acl/acl:aces/acl:ace/acl:name"; - } - description "The Access Control Entry name is used to - refer to an ACL specification."; - } - } - - grouping telemetry-setup { - description - "A grouping for On-path Telemetry profile."; - - leaf node-action { - type telemetry-node-action; - description - "This object indicates the action that the node needs to - take, i.e. marking/read/unmarking/encapsulate/transit/decapsulate."; - } - - leaf measurement-period { - type uint64; - description - "It specifies the On-path Telemetry period. - It is the marking period for AltMark."; - } - - leaf measurement-period-number { - type uint64; - description - "It specifies the On-path Telemetry period number."; - } - - leaf flow-mon-id { - type uint32; - description - "It specifies the 20-bit FlowMonID."; - } - - leaf method-type { - type altmark-method-type; - description - "It specifies the AltMark method type."; - } - - } - - grouping loss-counters { - description - "The set of counters for RFC 9341 loss calculation."; - - leaf in-traffic-pkts { - type yang:counter64; - description - "Total inbound packets of the period according to RFC 9341"; - } - leaf out-traffic-pkts { - type yang:counter64; - description - "Total outbound packets of the period according to RFC 9341"; - } - - leaf in-traffic-bytes { - type uint64; - description - "Total inbound bytes of the period according to RFC 9341"; - } - - leaf out-traffic-bytes { - type uint64; - description - "Total outbound bytes of the period according to RFC 9341"; - } - - } - - grouping delay-timestamps { - description - "It indicates the set of timestamps for RFC 9341 delay calculation."; - - container pkts-timestamps { - description - "The list of timestamps of the period according to RFC 9341"; - - leaf pkt-timestamp { - type yang:date-and-time; - description - "To specify the timestamp of the delay packet for delay measurements"; - } - leaf pkt-seq-num { - type yang:counter32; - description - "To specify the sequence number of the delay packet for delay measurements"; - } - } - } - - grouping path-delay-metrics { - description - "It indicates the path delay measurements."; - - leaf path-delay-mean { - type uint32; - description - "mean path delay as per [I-D.ietf-opsawg-ipfix-on-path-telemetry]"; - } - leaf path-delay-min { - type uint32; - description - "min path delay as per [I-D.ietf-opsawg-ipfix-on-path-telemetry]"; - } - - leaf path-delay-max { - type uint32; - description - "max path delay as per [I-D.ietf-opsawg-ipfix-on-path-telemetry]"; - } - leaf path-delay-sum { - type uint64; - description - "sum of the path delay as per [I-D.ietf-opsawg-ipfix-on-path-telemetry]"; - } - } - - grouping ioam-incremental-tracing-data-list { - description - "A grouping for incremental tracing data."; - - container ioam-incremental-tracing { - description - "The list of incremental tracing data"; - leaf-list incremental-tracing { - type ioam-trace-data; - description - "This object indicates the incremental tracing data."; - } - } - } - - grouping ioam-preallocated-tracing-data-list { - description - "A grouping for the list of pre-allocated tracing data."; - - leaf-list preallocated-tracing { - type ioam-trace-data; - description - "This object indicates the preallocated tracing data."; - } - } - - grouping ioam-direct-export-tracing-data-list { - description - "A grouping for the list of direct export data."; - - leaf-list direct-export { - type ioam-trace-data; - description - "This object indicates the direct export data."; - } - } - - grouping ioam-proof-of-transit-data-list { - description - "A grouping for the list of proof of transit data."; - - leaf-list proof-of-transit { - type ioam-pot-data; - description - "This object indicates the proof of transit data."; - } - } - - grouping ioam-edge-to-edge-data-list { - description - "A grouping for the list of edge-to-edge data."; - - leaf-list edge-to-edge { - type ioam-e2e-data; - description - "This object indicates the edge to edge data."; - } - } - - /* - * DATA NODES - */ - - container on-path-telemetry-data { - config false; - description "On-path Telemetry top level container"; - - list interface { - key "if-name"; - description - "It contains the list of the interfaces activated for AltMark and IOAM"; - leaf if-name { - type if:interface-ref; - description "This is a reference to the Interface name."; - } - - leaf profile-name { - type string{ - length "1..300"; - } - description - "Unique identifier for the On-path Telemetry profile."; - } - - container filter { - uses telemetry-filter; - description - "The filter which is used to indicate the flow where - the On-path Telemetry is applied."; - } - - leaf protocol-type { - type telemetry-protocol-type; - description - "This item is used to indicate the carrier protocol where - the On-path Telemetry is applied."; - } - - uses telemetry-setup; - - container altmark-loss-measurement { - if-feature altmark; - description - "It reports the loss measurement data."; - - uses loss-counters; - } - - container altmark-delay-measurement { - if-feature altmark; - description - "It reports the delay measurement data."; - - uses delay-timestamps; - } - - container path-delay { - if-feature pathdelay; - description - "It reports the path delay measurements."; - - uses path-delay-metrics; - } - - container ioam-incremental-tracing { - if-feature incremental-trace; - presence "Enables incremental tracing option."; - description - "It reports the incremental tracing option data."; - - uses ioam-incremental-tracing-data-list; - } - - container ioam-preallocated-tracing { - if-feature preallocated-trace; - presence "Enables preallocated tracing option."; - description - "It reports the preallocated tracing option data."; - - uses ioam-preallocated-tracing-data-list; - } - - container ioam-direct-export { - if-feature direct-export; - presence "Enables direct-export option."; - description - "It reports the direct-export option data"; - - uses ioam-direct-export-tracing-data-list; - } - - container ioam-proof-of-transit { - if-feature proof-of-transit; - presence "Enables Proof of Transit option."; - description - "It reports the PoT option data."; - - uses ioam-proof-of-transit-data-list; - } - - container ioam-edge-to-edge { - if-feature edge-to-edge; - presence "Enables edge-to-edge option."; - description - "It reports the edge-to-edge option data."; - - uses ioam-edge-to-edge-data-list; - } - } - } -} diff --git a/experimental/ietf-extracted-YANG-modules/ietf-on-path-telemetry@2026-06-11.yang b/experimental/ietf-extracted-YANG-modules/ietf-on-path-telemetry@2026-06-11.yang new file mode 100644 index 000000000..1e3af5877 --- /dev/null +++ b/experimental/ietf-extracted-YANG-modules/ietf-on-path-telemetry@2026-06-11.yang @@ -0,0 +1,692 @@ +module ietf-on-path-telemetry { + yang-version 1.1; + namespace "urn:ietf:params:xml:ns:yang:ietf-on-path-telemetry"; + prefix "on-path-telemetry"; + + import ietf-access-control-list { + prefix acl; + reference + "RFC 8519: YANG Data Model for Network Access Control + Lists (ACLs)"; + } + import ietf-interfaces { + prefix if; + reference + "RFC 8343: A YANG Data Model for Interface Management"; + } + + import ietf-yang-types { + prefix yang; + reference + "Section 3 of RFC 6991"; + } + + import ietf-lime-time-types { + prefix lime; + reference + "RFC 8532: Generic YANG Data Model for the Management of + Operations, Administration, and Maintenance (OAM) Protocols + That Use Connectionless Communications"; + } + + import ietf-ioam { + prefix ioam; + reference + "RFC 9617"; + } + + import ietf-altmark { + prefix altmark; + reference + "draft-ietf-ippm-alt-mark-yang"; + } + + organization + "IETF IPPM (IP Performance Metrics) Working Group"; + + contact + "WG Web: + WG List: + Author: giuseppe.fioccola@huawei.com + Author: zhoutianran@huawei.com + Author: zhuyq8@chinatelecom.cn + Author: zhangwq@chinatelecom.cn + Author: zhukeyi@huawei.com"; + + description + "This YANG module specifies a vendor-independent data + model for On-Path Telemetry. + + 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. + + Copyright (c) 2026 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 + (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself + for full legal notices."; + + revision 2026-06-11 { + description "First revision."; + reference "RFC XXXX: A YANG Data Model for On-path Telemetry"; + } + + /* + * FEATURES + */ + + feature altmark { + description + "This feature indicated that the Alternate-Marking Method is + supported."; + reference + "RFC 9341: Alternate-Marking Method; + RFC 9342: Clustered Alternate-Marking Method + RFC 9343: IPv6 Application of the Alternate-Marking Method + RFC 9714: Application of the Alternate Marking Method to the + MPLS Label Stack + RFC 9947: Application of the Alternate Marking Method to the + Segment Routing Header"; + } + + feature pathdelay { + description + "This feature indicated that the Path Delay is + supported."; + reference + "RFC 9951: Export of Delay Performance Metrics in IPFIX"; + } + + feature ioam { + description + "This feature indicated that the Alternate-Marking Method is + supported."; + reference + "RFC 9197: Data Fields for In-situ OAM"; + } + + feature incremental-trace { + description + "This feature indicated that the incremental tracing option is + supported."; + reference "RFC 9197: Data Fields for In-situ OAM"; + } + + feature preallocated-trace { + description + "This feature indicated that the preallocated tracing option is + supported."; + reference "RFC 9197: Data Fields for In-situ OAM"; + } + + feature direct-export { + description + "This feature indicated that the direct export option is + supported."; + reference "RFC 9326: In-situ OAM Direct Exporting"; + } + + feature proof-of-transit { + description + "This feature indicated that the proof of transit option is + supported"; + reference "RFC 9197: Data Fields for In-situ OAM"; + } + + feature edge-to-edge { + description + "This feature indicated that the edge-to-edge option is + supported."; + reference "RFC 9197: Data Fields for In-situ OAM"; + } + + /* + * IDENTITIES + */ + + identity filter { + description + "Base identity to represent a filter. A filter is used to + specify the flow to which the On-Path Telemetry method is + applied."; + } + + identity acl-filter { + base filter; + description + "Apply ACL rules to specify the flow."; + } + + identity protocol { + description + "Base identity to represent the protocol. It's used to + indicate the protocol for the application of the On-Path + Telemetry method."; + } + + identity ipv6 { + base protocol; + description + "The On-Path Telemetry method is applied to IPv6 protocol."; + reference + "RFC 9343: IPv6 Application of the Alternate-Marking Method, + RFC 9486: In-situ OAM IPv6 Options"; + } + + identity srh { + base protocol; + description + "The On-Path Telemetry method is applied to SRH."; + reference + "RFC 9947: Application of the Alternate Marking Method to the + Segment Routing Header"; + } + + identity mpls { + base protocol; + description + "The On-Path Telemetry method is applied to MPLS."; + reference + "RFC 9714: Application of the Alternate Marking Method + to the MPLS Label Stack"; + } + identity nsh { + base protocol; + description + "The described IOAM data is embedded in NSH."; + reference + "RFC 9452: Network Service Header (NSH) + Encapsulation for In-situ OAM (IOAM) Data"; + } + + /* + * TYPE DEFINITIONS + */ + + typedef telemetry-filter-type { + type identityref { + base filter; + } + description + "It specifies a known type of filter."; + } + + typedef telemetry-protocol-type { + type identityref { + base protocol; + } + description + "It specifies a known type of carrier protocol for the On-path + Telemetry data."; + } + + typedef flow-direction { + type enumeration { + enum "ingress" { + value 1; + description + "Ingress of an AltMark flow."; + } + enum "transit" { + value 2; + description + "Transit of an AltMark flow."; + } + enum "egress" { + value 3; + description + "Egress of an AltMark flow."; + } + } + description + "Flow direction."; + } + + typedef ioam-trace-data { + type identityref { + base ioam:trace-type; + } + description + "It specifies the trace data."; + } + + typedef ioam-pot-data { + type identityref { + base ioam:pot-type; + } + description + "It specifies the pot data."; + } + + typedef ioam-e2e-data { + type identityref { + base ioam:e2e-type; + } + description + "It specifies the edge-to-edge data."; + } + + /* + * GROUP DEFINITIONS + */ + + grouping telemetry-filter { + description + "A grouping for On-path Telemetry filter definition"; + + leaf filter-type { + type telemetry-filter-type; + description "filter type"; + } + + leaf ace-name { + when "derived-from-or-self(../filter-type, + 'on-path-telemetry:acl-filter')"; + type leafref { + path "/acl:acls/acl:acl/acl:aces/acl:ace/acl:name"; + } + description + "The Access Control Entry name is used to + refer to an ACL specification."; + } + } + + grouping telemetry-dir-prot { + description + "A grouping for On-path Telemetry information."; + + leaf direction { + type flow-direction; + description + "Specify the flow direction."; + } + + leaf protocol-type { + type telemetry-protocol-type; + description + "This item is used to indicate the carrier protocol where + the On-path Telemetry is applied."; + } + } + + grouping altmark-telemetry { + description + "A grouping for On-path Telemetry profile."; + + leaf flow-mon-id { + type altmark:flow-id; + description + "It specifies the 20-bit FlowMonID, as defined in RFC 9343 + and RFC 9714. Note that it corresponds to the + altmarkFlowMonID parameter defined in + draft-ietf-opsawg-ipfix-alt-mark."; + } + + leaf measurement-period-number { + type uint64; + description + "It specifies the On-path Telemetry period number."; + } + } + + grouping loss-counters { + description + "The set of counters for RFC 9341 and RFC 9342 loss + calculation."; + + leaf loss-flag { + type bits { + bit l-flag { + position 0; + description + "It indicates the loss-flag value"; + } + } + description + "The loss-flag value is defined in RFC 9343 and RFC 9714. + Note that it corresponds to the altmarkLossFlag parameter + defined in draft-ietf-opsawg-ipfix-alt-mark."; + } + + leaf in-traffic-pkts { + type yang:counter64; + description + "Total inbound packets of the period according to RFC 9341 + and RFC9342"; + } + + leaf out-traffic-pkts { + type yang:counter64; + description + "Total outbound packets of the period according to RFC 9341 + and RFC9342"; + } + + leaf in-traffic-bytes { + type uint64; + description + "Total inbound bytes of the period according to RFC 9341 + and RFC9342"; + } + + leaf out-traffic-bytes { + type uint64; + description + "Total outbound bytes of the period according to RFC 9341 + and RFC9342"; + } + } + + grouping delay-timestamps { + description + "It indicates the set of timestamps for RFC 9341 and RFC 9342 + delay calculation."; + + leaf delay-flag { + type bits { + bit d-flag { + position 0; + description + "It indicates the delay-flag value."; + } + } + description + "The delay-flag value is defined in RFC 9343 and RFC 9714. + Note that it corresponds to the altmarkDelayFlag parameter + defined in draft-ietf-opsawg-ipfix-alt-mark."; + } + + container in-pkts-timestamps { + description + "The list of timestamps of the period according to RFC 9341 + and RFC9342"; + + leaf in-pkt-timestamp { + type yang:date-and-time; + description + "To specify the timestamp of the delay packet for delay + measurements"; + } + + leaf in-pkt-seq-num { + type yang:counter32; + description + "To specify the sequence number of the delay packet for + delay measurements"; + } + } + + container out-pkts-timestamps { + description + "The list of timestamps of the period according to RFC 9341 + and RFC9342"; + + leaf out-pkt-timestamp { + type yang:date-and-time; + description + "To specify the timestamp of the delay packet for delay + measurements"; + } + + leaf out-pkt-seq-num { + type yang:counter32; + description + "To specify the sequence number of the delay packet for + delay measurements"; + } + } + } + + grouping path-delay-metrics { + description + "It indicates the path delay measurements."; + + leaf path-delay-mean { + type uint32; + description + "mean path delay as per RFC 9951"; + } + leaf path-delay-min { + type uint32; + description + "min path delay as per RFC 9951"; + } + + leaf path-delay-max { + type uint32; + description + "max path delay as per RFC 9951"; + } + + leaf path-delay-sum { + type uint64; + description + "sum of the path delay as per RFC 9951"; + } + } + + grouping ioam-incremental-tracing-data-list { + description + "A grouping for incremental tracing data."; + + leaf-list incremental-tracing { + type ioam-trace-data; + description + "This object indicates the incremental tracing data."; + } + } + + grouping ioam-preallocated-tracing-data-list { + description + "A grouping for the list of pre-allocated tracing data."; + + leaf-list preallocated-tracing { + type ioam-trace-data; + description + "This object indicates the preallocated tracing data."; + } + } + + grouping ioam-direct-export-tracing-data-list { + description + "A grouping for the list of direct export data."; + + leaf-list direct-export { + type ioam-trace-data; + description + "This object indicates the direct export data."; + } + } + + grouping ioam-proof-of-transit-data-list { + description + "A grouping for the list of proof of transit data."; + + leaf-list proof-of-transit { + type ioam-pot-data; + description + "This object indicates the proof of transit data."; + } + } + + grouping ioam-edge-to-edge-data-list { + description + "A grouping for the list of edge-to-edge data."; + + leaf-list edge-to-edge { + type ioam-e2e-data; + description + "This object indicates the edge to edge data."; + } + } + + /* + * DATA NODES + */ + + container on-path-telemetry-data { + config false; + description "On-path Telemetry top level container"; + + container on-path-telemetry-info { + config false; + description + "Describes information such as units or timestamp format + that assists monitoring systems in the interpretation of the + on-path-telemetry data."; + + leaf timestamp-type { + type identityref { + base lime:timestamp-type; + } + description + "Type of timestamp, such as Truncated PTP or NTP."; + } + } + + list available-interface { + key "if-name"; + description + "It contains the list of the interfaces activated for + Telemetry"; + leaf if-name { + type if:interface-ref; + description "This is a reference to the Interface name."; + } + + container filter { + uses telemetry-filter; + description + "The filter which is used to indicate the flow where + the On-path Telemetry is applied."; + } + + uses telemetry-dir-prot; + + container profiles { + description + "Contains On-path Telemetry profiles."; + + list altmark-profile { + if-feature altmark; + key "altmark-profile-name"; + description + "It describes the list of the AltMark profiles configured + on the node"; + leaf altmark-profile-name { + type string{ + length "1..300"; + } + description + "Unique identifier for each AltMark profile."; + } + + uses altmark-telemetry; + + container altmark-loss-measurement { + description + "It reports the loss measurement data."; + + uses loss-counters; + } + + container altmark-delay-measurement { + description + "It reports the delay measurement data."; + + uses delay-timestamps; + } + + } + + list path-delay-profile { + if-feature pathdelay; + key "path-delay-profile-name"; + description + "It describes the list of the path delay profiles + configured on the node"; + leaf path-delay-profile-name { + type string { + length "1..300"; + } + description + "Unique identifier for each path delay profile."; + } + + uses path-delay-metrics; + } + + list ioam-profile { + if-feature ioam; + key "ioam-profile-name"; + description + "It describes the list of the path delay profiles + configured on the node"; + leaf ioam-profile-name { + type string{ + length "1..300"; + } + description + "Unique identifier for each path delay profile."; + } + + container ioam-incremental-tracing { + if-feature incremental-trace; + presence "Enables incremental tracing option."; + description + "It reports the incremental tracing option data."; + + uses ioam-incremental-tracing-data-list; + } + + container ioam-preallocated-tracing { + if-feature preallocated-trace; + presence "Enables preallocated tracing option."; + description + "It reports the preallocated tracing option data."; + + uses ioam-preallocated-tracing-data-list; + } + + container ioam-direct-export { + if-feature direct-export; + presence "Enables direct-export option."; + description + "It reports the direct-export option data"; + + uses ioam-direct-export-tracing-data-list; + } + + container ioam-proof-of-transit { + if-feature proof-of-transit; + presence "Enables Proof of Transit option."; + description + "It reports the PoT option data."; + + uses ioam-proof-of-transit-data-list; + } + + container ioam-edge-to-edge { + if-feature edge-to-edge; + presence "Enables edge-to-edge option."; + description + "It reports the edge-to-edge option data."; + + uses ioam-edge-to-edge-data-list; + } + } + } + } + } +} diff --git a/experimental/ietf-extracted-YANG-modules/ietf-te-packet-types@2026-05-08.yang b/experimental/ietf-extracted-YANG-modules/ietf-te-packet-types@2026-06-11.yang similarity index 99% rename from experimental/ietf-extracted-YANG-modules/ietf-te-packet-types@2026-05-08.yang rename to experimental/ietf-extracted-YANG-modules/ietf-te-packet-types@2026-06-11.yang index 2edf0aaf8..81f65f41b 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-te-packet-types@2026-05-08.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-te-packet-types@2026-06-11.yang @@ -21,6 +21,9 @@ module ietf-te-packet-types { "WG Web: WG List: + Editor: Italo Busi + + Editor: Tarek Saad @@ -63,7 +66,7 @@ module ietf-te-packet-types { This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2026-05-08 { + revision 2026-06-11 { description "This revision adds the following new identities: - bandwidth-profile-type; diff --git a/experimental/ietf-extracted-YANG-modules/ietf-te-types@2026-05-08.yang b/experimental/ietf-extracted-YANG-modules/ietf-te-types@2026-06-11.yang similarity index 99% rename from experimental/ietf-extracted-YANG-modules/ietf-te-types@2026-05-08.yang rename to experimental/ietf-extracted-YANG-modules/ietf-te-types@2026-06-11.yang index 40debcac6..a26aa8f8c 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-te-types@2026-05-08.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-te-types@2026-06-11.yang @@ -36,6 +36,9 @@ module ietf-te-types { "WG Web: WG List: + Editor: Italo Busi + + Editor: Tarek Saad @@ -77,7 +80,7 @@ module ietf-te-types { This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2026-05-08 { + revision 2026-06-11 { description "This revision adds the following new identities: - lsp-provisioning-error-reason; diff --git a/experimental/ietf-extracted-YANG-modules/ietf-tvr-node@2025-06-30.yang b/experimental/ietf-extracted-YANG-modules/ietf-tvr-node@2026-06-05.yang similarity index 87% rename from experimental/ietf-extracted-YANG-modules/ietf-tvr-node@2025-06-30.yang rename to experimental/ietf-extracted-YANG-modules/ietf-tvr-node@2026-06-05.yang index a8043cd24..dc11545de 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-tvr-node@2025-06-30.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-tvr-node@2026-06-05.yang @@ -6,17 +6,19 @@ module ietf-tvr-node { import ietf-inet-types { prefix inet; reference - "RFC 6991: Common YANG Data Types"; + "RFC 9911: Common YANG Data Types"; } import ietf-yang-types { prefix "yang"; reference - "RFC 6991: Common YANG Data Types"; + "RFC 9911: Common YANG Data Types"; } import ietf-tvr-schedule { prefix "tvr-schd"; + reference + "RFC XXXX: A YANG Data Model for Scheduled Attributes"; } organization @@ -40,10 +42,7 @@ module ietf-tvr-node { "The YANG module is to configure and manage node attributes with schedules. - This YANG model conforms to the Network Management - Datastore Architecture (NMDA) as described in RFC 8342. - - Copyright (c) 2025 IETF Trust and the persons identified as + Copyright (c) 2026 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or @@ -53,18 +52,18 @@ module ietf-tvr-node { 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 itself - for full legal notices."; + All revisions of IETF and IANA published modules can be found + at the YANG Parameters registry group + (https://www.iana.org/assignments/yang-parameters). - reference - "RFC XXXX: YANG Data Model for Scheduled Attributes"; + This version of this YANG module is part of RFC XXXX; see + the RFC itself for full legal notices."; - revision 2025-06-30 { + revision 2026-06-05 { description "Initial Version"; reference - "RFC XXXX: YANG Data Model for Scheduled Attributes."; + "RFC XXXX: A YANG Data Model for Scheduled Attributes."; } container node-schedule { @@ -135,8 +134,7 @@ module ietf-tvr-node { units "bits/second"; default "0"; description - "The default interface bandwidth in bits - per second"; + "The interface bandwidth in bits per second"; } container attribute-schedule { diff --git a/experimental/ietf-extracted-YANG-modules/ietf-tvr-schedule@2025-06-30.yang b/experimental/ietf-extracted-YANG-modules/ietf-tvr-schedule@2026-05-19.yang similarity index 78% rename from experimental/ietf-extracted-YANG-modules/ietf-tvr-schedule@2025-06-30.yang rename to experimental/ietf-extracted-YANG-modules/ietf-tvr-schedule@2026-05-19.yang index cebe3b4d5..c5da800ff 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-tvr-schedule@2025-06-30.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-tvr-schedule@2026-05-19.yang @@ -6,7 +6,7 @@ module ietf-tvr-schedule { import ietf-schedule { prefix "schedule"; reference - "RFC XXXX: A Common YANG Data Model for Scheduling"; + "RFC 9922: A Common YANG Data Model for Scheduling"; } organization @@ -30,10 +30,7 @@ module ietf-tvr-schedule { "The YANG module contains common YANG definitions for time-variant schedule. - This YANG model conforms to the Network Management - Datastore Architecture (NMDA) as described in RFC 8342. - - Copyright (c) 2025 IETF Trust and the persons identified as + Copyright (c) 2026 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or @@ -43,18 +40,18 @@ module ietf-tvr-schedule { 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 itself - for full legal notices."; + All revisions of IETF and IANA published modules can be found + at the YANG Parameters registry group + (https://www.iana.org/assignments/yang-parameters). - reference - "RFC XXXX: YANG Data Model for Scheduled Attributes"; + This version of this YANG module is part of RFC XXXX; see + the RFC itself for full legal notices."; - revision 2025-06-30 { + revision 2026-05-19 { description "Initial Version"; reference - "RFC XXXX: YANG Data Model for Scheduled Attributes."; + "RFC XXXX: A YANG Data Model for Scheduled Attributes."; } grouping tvr-schedule { diff --git a/experimental/ietf-extracted-YANG-modules/ietf-tvr-topology@2026-02-09.yang b/experimental/ietf-extracted-YANG-modules/ietf-tvr-topology@2026-02-09.yang deleted file mode 100644 index 554fe01c2..000000000 --- a/experimental/ietf-extracted-YANG-modules/ietf-tvr-topology@2026-02-09.yang +++ /dev/null @@ -1,191 +0,0 @@ -module ietf-tvr-topology { - yang-version 1.1; - namespace "urn:ietf:params:xml:ns:yang:ietf-tvr-topology"; - prefix tvr-topo; - - import ietf-inet-types { - prefix inet; - reference - "RFC 9911: Common YANG Data Types"; - } - - import ietf-yang-types { - prefix "yang"; - reference - "RFC 9911: Common YANG Data Types"; - } - - import ietf-tvr-schedule { - prefix "tvr-schd"; - } - - organization - "IETF Time-Variant Routing Working Group"; - - contact - "WG Web: - WG List: - - Author: Eric Kinzie - - Author: Don Fedyk - - Author: Yingzhen Qu - - Author: Acee Lindem - - Author: Marc Blanchet - "; - - description - "This YANG module contains YANG definitions for describing - network topology with a time-variant availability schedule. - - Copyright (c) 2026 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 - (https://www.rfc-editor.org/info/rfcXXXX); 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 2026-02-09 { - description - "Initial revision"; - reference - "RFC XXXX: YANG Data Model for Scheduled Attributes"; - } - - container topology-schedule { - description - "Network topology schedules."; - list node { - key "node-id"; - description - "List of nodes with schedules."; - leaf node-id { - type inet:uri; - description - "Identifier for a node; uniquely identifies a node. This - may be the same as the node-id defined in the ietf-network - module defined in RFC 8345."; - } - container available { - description - "The time at which this node becomes available."; - - leaf default-node-available { - type boolean; - default false; - description - "By default, the node is powered off."; - } - - uses tvr-schd:tvr-schedule { - augment "schedule" { - description - "Augment scheduled node availability."; - leaf node-available { - type boolean; - description - "Node availability."; - } - } - } - } - } - - list link { - key "source-node source-link-id"; - description - "List of links."; - leaf source-node { - type inet:uri; - description - "A name refers to the source node of the link."; - } - leaf source-link-id { - type string; - description - "A name refers to the link of the source node."; - } - container available { - description - "The time at which this link becomes available."; - uses tvr-schd:tvr-schedule { - augment "schedule" { - description - "Augment scheduled values."; - container link-attributes { - description "Augmentation container for links."; - leaf link-available { - type boolean; - description - "The predicted link availability."; - } - leaf bandwidth { - type yang:gauge64; - units "bits/second"; - description - "The predicted link capacity. If the value measured - by the system is less than this value, the system - value is used. If the value measured by the system - is greater than this value the predicted value - SHOULD be used."; - } - leaf delay { - type uint32 { - range "0..16777215"; - } - description - "The predicted one-way delay or latency in - microseconds. If the value measured by the system is - less than this value the predicted value SHOULD be - used."; - } - leaf destination-node { - type inet:uri; - description - "A name refers to the destination node of the link."; - } - } - } - } - leaf default-link-available { - type boolean; - default "false"; - description - "The default link availability. During times when the - schedule does not specify an availability, this value - is used."; - } - leaf default-bandwidth { - type yang:gauge64; - units "bits/second"; - default "0"; - description - "The default link capacity specified in a - generic format."; - } - leaf default-delay { - type uint32 { - range "0..16777215"; - } - description - "The default one-way delay in microseconds."; - } - } - } - } -} diff --git a/experimental/ietf-extracted-YANG-modules/ietf-tvr-topology@2026-06-11.yang b/experimental/ietf-extracted-YANG-modules/ietf-tvr-topology@2026-06-11.yang new file mode 100644 index 000000000..eba3233cc --- /dev/null +++ b/experimental/ietf-extracted-YANG-modules/ietf-tvr-topology@2026-06-11.yang @@ -0,0 +1,221 @@ +module ietf-tvr-topology { + yang-version 1.1; + namespace "urn:ietf:params:xml:ns:yang:ietf-tvr-topology"; + prefix tvr-topo; + + import ietf-inet-types { + prefix inet; + reference + "RFC 9911: Common YANG Data Types"; + } + import ietf-yang-types { + prefix yang; + reference + "RFC 9911: Common YANG Data Types"; + } + import ietf-tvr-schedule { + prefix tvr-schd; + reference + "RFC XXXX: A YANG Data Model for Scheduled Attributes"; + } + + import ietf-network { + prefix nw; + reference + "RFC 8345: A YANG Data Model for Network Topologies"; + } + + import ietf-network-topology { + prefix nt; + reference + "RFC 8345: A YANG Data Model for Network Topologies"; + } + + organization + "IETF Time-Variant Routing Working Group"; + contact + "WG Web: + WG List: + + Author: Eric Kinzie + + Author: Don Fedyk + + Author: Yingzhen Qu + + Author: Acee Lindem + + Author: Marc Blanchet + "; + description + "This YANG module contains YANG definitions for describing + network topology with a time-variant availability schedule. + Copyright (c) 2026 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). + + All revisions of IETF and IANA published modules can be found + at the YANG Parameters registry group + (https://www.iana.org/assignments/yang-parameters). + + 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 2026-06-11 { + description + "Initial revision"; + reference + "RFC XXXX: A YANG Data Model for Scheduled Attributes"; + } + + grouping node-availability-schedule { + description + "Node availability scheduling - reusable grouping specifying + node availability scheduling."; + container available { + description + "The time at which this node becomes available."; + leaf default-node-available { + type boolean; + default "false"; + description + "By default, the node is powered off."; + } + uses tvr-schd:tvr-schedule { + augment "schedule" { + description + "Augment scheduled node availability."; + leaf node-available { + type boolean; + description + "Node availability."; + } + } + } + } + } + + grouping link-availability-schedule { + description + "Link availability scheduling - reusable grouping specifying + link availability scheduling."; + container available { + description + "The time at which this link becomes available."; + uses tvr-schd:tvr-schedule { + augment "schedule" { + description + "Augment scheduled values."; + container link-attributes { + description + "Augmentation container for links."; + leaf link-available { + type boolean; + description + "The predicted link availability."; + } + leaf bandwidth { + type yang:gauge64; + units "bits/second"; + description + "The predicted link capacity. If the value measured + by the system is less than this value, the system + value is used. If the value measured by the system + is greater than this value the predicted value + SHOULD be used."; + } + leaf delay { + type uint64; + units "microseconds"; + description + "The predicted one-way delay or latency in + microseconds. If the value measured by the system is + less than this value the predicted value SHOULD be + used."; + } + leaf-list destination-nodes { + type inet:uri; + description + "A list of one or more destination nodes that are + associated with the link schedule."; + } + leaf strict-destination-checking { + when "../destination-nodes" { + description + "This is only relevant when destination node(s) + are specified."; + } + type boolean; + default 'false'; + description + "Indicates whether or not the specified destination + node(s) are the only destinations allowed when the + link schedule is active"; + } + } + } + } + leaf default-link-available { + type boolean; + default "false"; + description + "The default link availability. During times when the + schedule does not specify an availability, this value + is used."; + } + leaf default-bandwidth { + type yang:gauge64; + units "bits/second"; + default "0"; + description + "The default link capacity specified in a + generic format."; + } + leaf default-delay { + type uint64; + units "microseconds"; + description + "The default one-way delay in microseconds."; + } + } + } + + augment "/nw:networks/nw:network/nw:network-types" { + description + "Introduces a new network type for TVR topology."; + container tvr-topology { + presence + "Indicates this is a TVR topology, with TVR + attributes."; + description + "Container for the TVR network type. + When present, it signals that the network contains + TVR augmentations."; + } + } + + augment "/nw:networks/nw:network/nw:node" { + when "../nw:network-types/tvr-topo:tvr-topology"; + description + "Augment network node with schedules."; + uses node-availability-schedule; + } + + augment "/nw:networks/nw:network/nw:node/nt:termination-point" { + when "../../nw:network-types/tvr-topo:tvr-topology"; + description + "Augment network link with schedules."; + uses link-availability-schedule; + } +} diff --git a/experimental/ietf-extracted-YANG-modules/ietf-vrrp@2026-05-22.yang b/experimental/ietf-extracted-YANG-modules/ietf-vrrp@2026-06-12.yang similarity index 98% rename from experimental/ietf-extracted-YANG-modules/ietf-vrrp@2026-05-22.yang rename to experimental/ietf-extracted-YANG-modules/ietf-vrrp@2026-06-12.yang index 0d04a29ff..3e667f67f 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-vrrp@2026-05-22.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-vrrp@2026-06-12.yang @@ -57,7 +57,6 @@ module ietf-vrrp { forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). - All revisions of IETF and IANA published modules can be found at the YANG Parameters registry group (https://www.iana.org/assignments/yang-parameters). @@ -71,7 +70,7 @@ module ietf-vrrp { This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2026-05-22 { + revision 2026-06-12 { description "This revision includes the following changes: - Update some identifiers and descriptions to conform @@ -250,7 +249,6 @@ module ietf-vrrp { "Indicates that the owner has preempted another virtual router to become the active virtual router."; } - /* vrrp-error-global identity and its derivatives. */ identity vrrp-error-global { @@ -431,8 +429,8 @@ module ietf-vrrp { virtual router."; } leaf accept-mode { - when "derived-from-or-self(current()/../version, - 'vrrp:vrrp-v3')" { + when "derived-from-or-self(current()/../version, " + + "'vrrp:vrrp-v3')" { description "Applicable only to version 3."; } @@ -736,8 +734,8 @@ module ietf-vrrp { description "The effective priority of the virtual router taking account address ownership and any modifications due to - local policy. The priority 255 is reserved the virtual - router owning the address."; + local policy. The priority 255 is reserved for the + virtual router owning the address."; } leaf last-adv-source { type inet:ip-address; @@ -771,7 +769,10 @@ module ietf-vrrp { "Calculated based on the priority and advertisement interval configuration command parameters. Note that the units are microseconds rather than centiseconds units - as configured for advertisement-interval. See RFC 9568."; + as configured for advertisement-interval."; + reference + "RFC 9568: Virtual Router Redundancy Protocol (VRRP) + Version 3 for IPv4 and IPv6, Section 6.1"; } leaf last-event { type identityref { @@ -812,7 +813,9 @@ module ietf-vrrp { state has transitioned to 'Active'. The identifier of this leaf is changed to reflect - the updated terminology used in RFC 9568."; + the updated terminology used in RFC 9568. The leaf type + has also been updated to a 64-bit counter consistent + with other VRRP counters."; } leaf advertisement-rcvd { type yang:counter64; @@ -938,6 +941,7 @@ module ietf-vrrp { } } // statistics } // vrrp-global-state-attributes + /* * Configuration data and operational state data nodes */ @@ -986,6 +990,7 @@ module ietf-vrrp { "VRRP data at the global level."; uses vrrp-global-state-attributes; } + /* * Notifications */ @@ -1012,7 +1017,6 @@ module ietf-vrrp { description "Indicates why the virtual router has transitioned to active state. - The identifier of the leaf is changed to reflect the updated terminology used in RFC 9568."; } diff --git a/standard/iana/yang-parameters.xml b/standard/iana/yang-parameters.xml index d3e063d7d..c18e86ca9 100644 --- a/standard/iana/yang-parameters.xml +++ b/standard/iana/yang-parameters.xml @@ -4,7 +4,7 @@ YANG Parameters 2010-06-10 - 2026-05-26 + 2026-06-17 YANG Module Names @@ -2738,25 +2738,25 @@ and Subsequent Address Family Identi 's module file will be posted upon the document's publication as an RFC. - + ietf-udp-client N - + ietf-udp-client@2026-06-15.yang urn:ietf:params:xml:ns:yang:ietf-udp-client udpc - - 's module file will be posted upon the document's publication as an RFC. + + - + ietf-udp-server N - + ietf-udp-server@2026-06-15.yang urn:ietf:params:xml:ns:yang:ietf-udp-server udps - - 's module file will be posted upon the document's publication as an RFC. + + ietf-vn