diff --git a/experimental/ietf-extracted-YANG-modules/ietf-bmp-tcp-dependencies@2025-01-02.yang b/experimental/ietf-extracted-YANG-modules/ietf-bmp-tcp-dependencies@2025-01-02.yang index b0d21a344..6f2cf1997 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-bmp-tcp-dependencies@2025-01-02.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-bmp-tcp-dependencies@2025-01-02.yang @@ -5,6 +5,14 @@ module ietf-bmp-tcp-dependencies { import ietf-bmp { prefix bmp; + reference + "RFC XXXX: BMP YANG Module."; + } + import ietf-tcp { + prefix tcp; + reference + "RFC 9648: YANG Data + Model for TCP."; } import ietf-tcp-common { prefix tcpcmn; @@ -28,13 +36,19 @@ module ietf-bmp-tcp-dependencies { Author: Paolo Lucente - + Author: Thomas Graf Author: Benoit Claise - "; + + + Author: Dhananjay Patki + + + Author: Prasad S. Narasimha + "; description "This module specifies a structure for BMP (BGP Monitoring Protocol) configuration and monitoring. @@ -65,32 +79,56 @@ module ietf-bmp-tcp-dependencies { description "initial version"; reference - "RFC YYYY: BMP YANG Module - RFC-EDITOR: please update YYYY with this RFC ID"; + "RFC XXXX: BMP YANG Data Model"; } augment "/bmp:bmp/bmp:monitoring-stations/" + "bmp:monitoring-station/" + "bmp:connection/bmp:tcp-options" { description - "Augment the tcp options of the BMP model"; + "Augment the tcp options of the ietf-bmp module"; + leaf mss { + type tcp:mss; + description + "Maximum segment size (MSS) for the TCP connections. + In the absence of this container, the system + will select the maximum segment size for this + connection."; + reference + "RFC 9293: Transmission Control + Protocol (TCP) Specification. + RFC 9648: YANG Data Model for TCP."; + } uses tcpcmn:tcp-common-grouping; + leaf maximum-segment-size { + type uint16; + description + "Maximum segment size for the TCP connections. + In the absence of this container, the system + will select the maximum segment size for this + connection."; + } container secure-session { - presence "Means the session should be secure. "; + if-feature "tcp:authentication"; + presence "The presence of this container means the + session should be secured. "; description "Container for describing how a particular BMP session - is to be secured."; + is to be secured. Based on RFC 9293 implementation."; + reference + "RFC 9293: Transmission Control + Protocol (TCP) Specification"; choice authentication { mandatory true; description "Choice of TCP authentication."; case ao { description - "Uses TCP-AO to secure the session. Parameters for - those are defined as a grouping in the TCP YANG - model."; + "Uses TCP-AO to secure the session."; reference - "RFC 5925 - The TCP Authentication Option."; + "RFC 5925 - The TCP Authentication Option. + RFC 9648: YANG Data Model for TCP (grouping ao)."; + uses tcp:ao; leaf ao-keychain { type key-chain:key-chain-ref; description @@ -103,11 +141,10 @@ module ietf-bmp-tcp-dependencies { } case md5 { description - "Uses TCP-MD5 to secure the session. Parameters for - those are defined as a grouping in the TCP YANG - model."; + "Uses TCP-MD5 to secure the session. ."; reference - "RFC 5925: The TCP Authentication Option."; + "RFC 2385: Protection of BGP Sessions + via the TCP MD5 Signature Option."; leaf md5-keychain { type key-chain:key-chain-ref; description @@ -121,4 +158,4 @@ module ietf-bmp-tcp-dependencies { } } } -} +} \ No newline at end of file diff --git a/experimental/ietf-extracted-YANG-modules/ietf-bmp@2025-01-02.yang b/experimental/ietf-extracted-YANG-modules/ietf-bmp@2025-01-02.yang index b49d2673f..77809d23e 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-bmp@2025-01-02.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-bmp@2025-01-02.yang @@ -5,6 +5,8 @@ module ietf-bmp { import ietf-yang-types { prefix yang; + reference + "RFC 6991: Common YANG Data Types"; } import ietf-inet-types { prefix inet; @@ -40,17 +42,18 @@ module ietf-bmp { contact "WG Web: WG List: + Author: Camilo Cardona Author: Paolo Lucente - + Author: Thomas Graf Author: Benoit Claise - + Author: Dhananjay Patki @@ -86,8 +89,7 @@ module ietf-bmp { description "initial version"; reference - "RFC YYYY: BMP YANG Module - RFC-EDITOR: please update YYYY with this RFC ID"; + "RFC XXXX: BMP YANG Data Model."; } feature bmp-filter-based-on-route-policy { @@ -96,8 +98,9 @@ module ietf-bmp { is capable of filtering prefixes in BMP monitoring sessions"; } - /* The next enums are temporary here until we resolve how to deal - * with them. Taken from draft-ietf-idr-bgp-model */ + /* The next identities are temporary here until we resolve + * how to deal with them. Taken from + * draft-ietf-idr-bgp-model. */ /* BGP AFI-SAFI Type Identities. */ identity afi-safi-type { @@ -136,6 +139,7 @@ module ietf-bmp { "This identity selects all peers under the RIB. When used, it acts as a default configuration."; } + identity bmp-ni-types { description "Identities for selecting one or more network instances for @@ -162,7 +166,7 @@ module ietf-bmp { to select all network instances except the global one."; } - /* The next types are temporary here until we resolve how to deal + /* The next type are temporary here until we resolve how to deal * with them. Taken from draft-ietf-idr-bgp-model */ /* BGP Peer-Types */ @@ -411,12 +415,7 @@ module ietf-bmp { instances SHOULD provide a way of unambiguously selecting which configuration container should be selected - for a peer in case of multiple matches. - - Note that if the implementation supports module - ietf-bmp-bgp-dependencies, the peer configurations - under the BGP container have priority over the - configurations under this container."; + for a peer in case of multiple matches."; container peers { description "Configuration for individual peers."; @@ -468,11 +467,12 @@ module ietf-bmp { key "id"; description "Identification of peers - for which we send BMP data to the collector - using a peer type defined using a - bmp-peer-selectors identity. + for which BMP data is sent to + the collector using a peer type + defined by a bmp-peer-selectors + identity. For instance, to create a default for all - peers use all-peers"; + peers use the all-peers identity"; leaf id { type identityref { base bmp-peer-selectors; @@ -497,7 +497,7 @@ module ietf-bmp { key "id"; description "Identification of peers - for which we send BMP data to the collector + for which BMP data is sent to the collector using BGP peer-type (e.g. internal, external) "; leaf id { @@ -703,15 +703,6 @@ module ietf-bmp { description "TCP options for the connection to the monitoring station."; - leaf maximum-segment-size { - type uint16; - description - "Maximum segment size for the TCP connections. - In the absence of this container, the system - will select the maximum segment size for this - connection."; - } - // Taken from the bgp yang module leaf mtu-discovery { type boolean; default "true"; @@ -719,7 +710,9 @@ module ietf-bmp { "Enables path MTU discovery for the TCP sessions (true) or disables it (false)."; reference - "RFC 1191: Path MTU discovery."; + "RFC 9293: Transmission Control Protocol (TCP). + RFC 9648: YANG Data Model for TCP, + see leaf pmtud for reference."; } } leaf initial-delay { @@ -1064,52 +1057,14 @@ module ietf-bmp { action session-reset { description "Resets the session for a station."; - output { - choice outcome { - description - "Output of the reset operation. Either a success or - failure. For the latter, the reason for the - error is provided."; - leaf success { - type empty; - description - "Reset successful."; - } - leaf failure { - type string; - description - "Reset could not be performed. - The reason is included in the field."; - } - } - } } action session-counter-reset { description "Resets the counters of a BMP monitoring station."; - output { - choice outcome { - description - "Output of the reset operation. Either a success or - failure. For the latter, the reason for the - error is provided."; - leaf success { - type empty; - description - "Counter reset successful."; - } - leaf failure { - type string; - description - "Reset could not be performed. - The reason is included in the field."; - } - } - } } nacm:default-deny-all; } } } } -} +} \ No newline at end of file diff --git a/experimental/ietf-extracted-YANG-modules/ietf-nrp-device@2025-03-02.yang b/experimental/ietf-extracted-YANG-modules/ietf-nrp-device@2026-06-01.yang similarity index 93% rename from experimental/ietf-extracted-YANG-modules/ietf-nrp-device@2025-03-02.yang rename to experimental/ietf-extracted-YANG-modules/ietf-nrp-device@2026-06-01.yang index 10057f9bf..b405a45be 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-nrp-device@2025-03-02.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-nrp-device@2026-06-01.yang @@ -47,7 +47,7 @@ module ietf-nrp-device { fully conforms to the Network Management Datastore Architecture (NMDA). - 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 @@ -66,7 +66,7 @@ module ietf-nrp-device { // RFC Ed.: update the date below with the date of RFC // publication and remove this note. - revision 2025-03-02 { + revision 2026-06-01 { description "Initial revision."; reference @@ -78,13 +78,12 @@ module ietf-nrp-device { * Grouping - NRP QoS Per-Hop Behavior (PHB) profile */ - grouping qos-phb-profile { + grouping phb-profile-ref { description "Grouping for NRP QoS Per-Hop Behavior (PHB) profile."; leaf phb-profile { type leafref { - path - "/nrp-policies/qos-profiles/phb-profile-identifier/id"; + path "/nrp-policies/qos-profiles/phb-profile-identifier/id"; } description "PHB profile identifier, specifying the forwarding treatment @@ -122,7 +121,7 @@ module ietf-nrp-device { } uses nrp:resource-reservation; uses nrp:selector-id; - uses qos-phb-profile; + uses phb-profile-ref; uses nrp:igp-congruent; /* NRP Interface Configuration Data */ container interfaces { @@ -139,7 +138,7 @@ module ietf-nrp-device { } uses nrp:resource-reservation; uses nrp:selector-id; - uses qos-phb-profile; + uses phb-profile-ref; } } } diff --git a/experimental/ietf-extracted-YANG-modules/ietf-nrp@2026-01-22.yang b/experimental/ietf-extracted-YANG-modules/ietf-nrp@2026-06-01.yang similarity index 87% rename from experimental/ietf-extracted-YANG-modules/ietf-nrp@2026-01-22.yang rename to experimental/ietf-extracted-YANG-modules/ietf-nrp@2026-06-01.yang index f8c0e2e27..978ec21a4 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-nrp@2026-01-22.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-nrp@2026-06-01.yang @@ -45,8 +45,7 @@ module ietf-nrp { import ietf-srv6-types { prefix srv6-types; reference - "draft-ietf-spring-srv6-yang: YANG Data Model for SRv6 Base - and Static"; + "draft-ietf-spring-srv6-yang-base: YANG Data Model for SRv6 Base"; } import ietf-topology-filter { prefix topo-filt; @@ -64,6 +63,7 @@ module ietf-nrp { Editor: Bo Wu + Editor: Dhruv Dhody @@ -93,7 +93,7 @@ module ietf-nrp { (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself for full legal notices."; - revision 2026-01-22 { + revision 2026-06-01 { description "Initial revision."; reference @@ -101,9 +101,52 @@ module ietf-nrp { Partitions (NRPs)"; } + /* Features - NRP Selector Mechanisms */ + + feature ipv4-selector { + description + "Indicates support for IPv4-derived NRP selection + (destination prefix based)."; + } + + feature ipv6-hbh-selector { + description + "Indicates support for dedicated IPv6 Hop?by?Hop + extension header selector ID."; + } + + feature srv6-selector { + description + "Indicates support for SRv6 SID?based NRP selection."; + } + + feature ipv6-destination-selector { + description + "Indicates support for IPv6 destination prefix?based + NRP selection."; + } + + feature mpls-mna-selector { + description + "Indicates support for in?stack MPLS MNA?based + NRP selection (NRPS13, NRPS20, ENRPS20)."; + } + + feature mpls-post-stack-selector { + description + "Indicates support for post?stack MPLS PSD?based + NRP selection."; + } + + feature acl-selector { + description + "Indicates support for ACL?based NRP selection."; + } + /* * I D E N T I T I E S */ + identity nrp-partition-mode { description "Base identity for NRP partition type."; @@ -214,8 +257,12 @@ module ietf-nrp { configuration."; container selector-id { description - "Container for NRP selector ID."; + "Container for NRP selector ID. It can contain one or more + selector mechanisms (IPv4 prefixes, IPv6 Hop-by-Hop options, + SRv6 SIDs, MPLS labels, or ACLs) depending on the features + supported by the implementation."; container ipv4-derived { + if-feature "ipv4-selector"; description "Container for IPv4 NRP selector ID."; leaf-list destination-prefix { @@ -226,12 +273,16 @@ module ietf-nrp { } } container ipv6 { + if-feature + "ipv6-hbh-selector or srv6-selector or + ipv6-destination-selector"; description "Container for IPv6 NRP selector ID."; choice selector-type { description "Choices for IPv6 selector ID type."; case dedicated { + if-feature "ipv6-hbh-selector"; leaf ipv6-hbh-eh { type uint32; description @@ -244,6 +295,7 @@ module ietf-nrp { } } case srv6-derived { + if-feature "srv6-selector"; leaf-list srv6-sid { type srv6-types:srv6-sid; description @@ -256,6 +308,7 @@ module ietf-nrp { } } case ipv6-destination-derived { + if-feature "ipv6-destination-selector"; leaf-list destination-prefix { type inet:ipv6-prefix; description @@ -266,6 +319,7 @@ module ietf-nrp { } } container mpls { + if-feature "mpls-mna-selector or mpls-post-stack-selector"; description "Container for MPLS NRP selector ID. Supports both In-Stack (MNA) and Post-Stack (PSD) encoding mechanisms."; @@ -273,6 +327,7 @@ module ietf-nrp { description "Selects the MPLS NRP Selector encoding mechanism."; case mna-in-stack { + if-feature "mpls-mna-selector"; description "In-Stack NRP Selector action. Refers to draft-ietf-mpls-mna-nrp-selector."; @@ -313,6 +368,7 @@ module ietf-nrp { } } case post-stack { + if-feature "mpls-post-stack-selector"; description "Post-Stack NRP Selector (PS-NRP). Refers to draft-ietf-mpls-mna-psd-nrp-selector."; @@ -327,6 +383,7 @@ module ietf-nrp { } } leaf-list acl-ref { + if-feature "acl-selector"; type acl-ref; description "NRP selection is done based on the specified list of @@ -353,7 +410,9 @@ module ietf-nrp { description "List of PHB profiles."; leaf id { - type string; + type string { + length "1..max"; + } description "Uniquely identifies the PHB. The profile only has significance within the service @@ -367,7 +426,7 @@ module ietf-nrp { * Grouping - NRP QoS Per-Hop Behavior (PHB) profile */ - grouping qos-phb-profile { + grouping phb-profile-ref { description "Grouping for NRP QoS Per-Hop Behavior (PHB) profile."; leaf phb-profile { @@ -399,14 +458,20 @@ module ietf-nrp { "The presence of the container node describes NRP IGP congruent, which indicates that the NRP instance uses the same IGP topology with the specified 'multi-topology-id' - and 'algo-id'. That is, the nodes and termination point of - the NRP topology and the IGP topology are the same, while - the link attributes of the NRP are different from those of - the IGP."; + and/or 'algo-id'. That is, the nodes and termination point + of the NRP topology and the IGP topology are the same, + while the link attributes of the NRP are different from + those of the IGP. + If not explicitly configured, both + (multi-topology-id, algo-id) pair default to 0 (standard + topology with standard SPF algorithm), corresponding to + the base IGP instance."; leaf multi-topology-id { type uint32; + default "0"; description - "Indicates the MT-id of the NRP IGP instance."; + "Indicates the MT-id of the NRP IGP instance. + MT-id 0 is reserved for the standard topology"; reference "RFC 5120: M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs) @@ -414,8 +479,10 @@ module ietf-nrp { } leaf algo-id { type uint32; + default "0"; description - "Indicates the algo-id of the NRP IGP instance."; + "Indicates the algo-id of the NRP IGP instance. + algo-id 0 is reserved for the standard SPF algorithm"; reference "RFC 9350: IGP Flexible Algorithm"; } @@ -452,7 +519,7 @@ module ietf-nrp { } uses resource-reservation; uses selector-id; - uses qos-phb-profile; + uses phb-profile-ref; } } } @@ -473,7 +540,9 @@ module ietf-nrp { "List of groups for NRP topology elements (node or links) that share common attributes."; leaf group-id { - type string; + type string { + length "1..max"; + } description "The NRP topology group identifier."; } @@ -505,7 +574,7 @@ module ietf-nrp { description "Indicates the resource reservation type of an NRP link."; } - uses qos-phb-profile; + uses phb-profile-ref; } } } @@ -527,12 +596,15 @@ module ietf-nrp { description "List of NRP policies."; leaf name { - type string; + type string { + length "1..max"; + } description "A string that uniquely identifies the NRP policy."; } leaf nrp-id { type uint32; + mandatory true; description "A 32-bit ID that uniquely identifies the NRP created by the enforcement of this NRP policy."; @@ -541,6 +613,7 @@ module ietf-nrp { type identityref { base nrp-partition-mode; } + mandatory true; description "Indicates the resource partition mode of the NRP, such as control plane partition, data plane partition, @@ -548,7 +621,7 @@ module ietf-nrp { } uses resource-reservation; uses selector-id; - uses qos-phb-profile; + uses phb-profile-ref; container topology { description "Container for NRP topology."; @@ -764,6 +837,7 @@ module ietf-nrp { description "Augments node with NRP state attributes."; choice nrp-attachment-type { + config false; description "Determines how NRP information is attached to node: single-nrp for NRP-specific topology, multi-nrp for @@ -791,6 +865,7 @@ module ietf-nrp { description "Augments link with NRP state attributes."; choice nrp-attachment-type { + config false; description "Determines how NRP information is attached to link: single-nrp for NRP-specific topology, multi-nrp for diff --git a/experimental/ietf-extracted-YANG-modules/ietf-power-and-energy@2026-01-22.yang b/experimental/ietf-extracted-YANG-modules/ietf-power-and-energy@2026-01-22.yang index 7e0feeafe..95f0cb639 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-power-and-energy@2026-01-22.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-power-and-energy@2026-01-22.yang @@ -61,26 +61,26 @@ module ietf-power-and-energy { accuracy base- and sub-types as needed. data-source-accuracy - ├── accuracy-like-parent - ├── accuracy-unknown - │ └── accuracy-unavailable - ├── accuracy-estimated - │ ├── accuracy-static - │ ├── accuracy-historic - │ └── accuracy-learned - └── accuracy-measured - ├── accuracy-measured-bronze - │ ├── accuracy-measured-bronze-1 - │ ├── accuracy-measured-bronze-10 - │ ├── accuracy-measured-bronze-100 - │ └── accuracy-measured-bronze-1000 - ├── accuracy-measured-silver - │ └── accuracy-measured-silver-... - ├── accuracy-measured-gold - │ └── accuracy-measured-gold-... - ├── accuracy-measured-red - │ └── accuracy-measured-red-... - └── accuracy-measured-ones + ├── accuracy-like-parent + ├── accuracy-unknown + │ └── accuracy-unavailable + ├── accuracy-estimated + │ ├── accuracy-static + │ ├── accuracy-historic + │ └── accuracy-learned + └── accuracy-measured + ├── accuracy-measured-bronze + │ ├── accuracy-measured-bronze-1 + │ ├── accuracy-measured-bronze-10 + │ ├── accuracy-measured-bronze-100 + │ └── accuracy-measured-bronze-1000 + ├── accuracy-measured-silver + │ └── accuracy-measured-silver-... + ├── accuracy-measured-gold + │ └── accuracy-measured-gold-... + ├── accuracy-measured-red + │ └── accuracy-measured-red-... + └── accuracy-measured-ones The accuracy levels under accuracy-measured are based on percent-wise accuracy classes: @@ -181,140 +181,140 @@ module ietf-power-and-energy { description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 30% OR |actual-sensor| ≤ 0.5"; + |actual-sensor| ≤ sensor * 30% OR |actual-sensor| ≤ 0.5"; } identity accuracy-measured-bronze-1 { base accuracy-measured-bronze; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 30% OR |actual-sensor| ≤ 1"; + |actual-sensor| ≤ sensor * 30% OR |actual-sensor| ≤ 1"; } identity accuracy-measured-bronze-10 { base accuracy-measured-bronze; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 30% OR |actual-sensor| ≤ 10"; + |actual-sensor| ≤ sensor * 30% OR |actual-sensor| ≤ 10"; } identity accuracy-measured-bronze-100 { base accuracy-measured-bronze; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 30% OR |actual-sensor| ≤ 100"; + |actual-sensor| ≤ sensor * 30% OR |actual-sensor| ≤ 100"; } identity accuracy-measured-bronze-1000 { base accuracy-measured-bronze; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 30% OR |actual-sensor| ≤ 1000"; + |actual-sensor| ≤ sensor * 30% OR |actual-sensor| ≤ 1000"; } identity accuracy-measured-silver { base accuracy-measured; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 10% OR |actual-sensor| ≤ 0.5"; + |actual-sensor| ≤ sensor * 10% OR |actual-sensor| ≤ 0.5"; } identity accuracy-measured-silver-1 { base accuracy-measured-silver; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 10% OR |actual-sensor| ≤ 1"; + |actual-sensor| ≤ sensor * 10% OR |actual-sensor| ≤ 1"; } identity accuracy-measured-silver-10 { base accuracy-measured-silver; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 10% OR |actual-sensor| ≤ 10"; + |actual-sensor| ≤ sensor * 10% OR |actual-sensor| ≤ 10"; } identity accuracy-measured-silver-100 { base accuracy-measured-silver; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 10% OR |actual-sensor| ≤ 100 "; + |actual-sensor| ≤ sensor * 10% OR |actual-sensor| ≤ 100 "; } identity accuracy-measured-silver-1000 { base accuracy-measured-silver; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 10% OR |actual-sensor| ≤ 1000"; + |actual-sensor| ≤ sensor * 10% OR |actual-sensor| ≤ 1000"; } identity accuracy-measured-gold { base accuracy-measured; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 5% OR |actual-sensor| ≤ 0.5"; + |actual-sensor| ≤ sensor * 5% OR |actual-sensor| ≤ 0.5"; } identity accuracy-measured-gold-1 { base accuracy-measured-gold; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 5% OR |actual-sensor| ≤ 1"; + |actual-sensor| ≤ sensor * 5% OR |actual-sensor| ≤ 1"; } identity accuracy-measured-gold-10 { base accuracy-measured-gold; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 5% OR |actual-sensor| ≤ 10"; + |actual-sensor| ≤ sensor * 5% OR |actual-sensor| ≤ 10"; } identity accuracy-measured-gold-100 { base accuracy-measured-gold; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 5% OR |actual-sensor| ≤ 100"; + |actual-sensor| ≤ sensor * 5% OR |actual-sensor| ≤ 100"; } identity accuracy-measured-gold-1000 { base accuracy-measured-gold; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 5% OR |actual-sensor| ≤ 1000"; + |actual-sensor| ≤ sensor * 5% OR |actual-sensor| ≤ 1000"; } identity accuracy-measured-red { base accuracy-measured; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 2% OR |actual-sensor| ≤ 0.5"; + |actual-sensor| ≤ sensor * 2% OR |actual-sensor| ≤ 0.5"; } identity accuracy-measured-red-1 { base accuracy-measured-red; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 2% OR |actual-sensor| ≤ 1"; + |actual-sensor| ≤ sensor * 2% OR |actual-sensor| ≤ 1"; } identity accuracy-measured-red-10 { base accuracy-measured-red; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 2% OR |actual-sensor| ≤ 10"; + |actual-sensor| ≤ sensor * 2% OR |actual-sensor| ≤ 10"; } identity accuracy-measured-red-100 { base accuracy-measured-red; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 2% OR |actual-sensor| ≤ 100"; + |actual-sensor| ≤ sensor * 2% OR |actual-sensor| ≤ 100"; } identity accuracy-measured-red-1000 { base accuracy-measured-red; description "The power data is a direct, real-time measurement from a sensor with precision and accuracy such that - |actual-sensor| ≤ sensor * 2% OR |actual-sensor| ≤ 1000"; + |actual-sensor| ≤ sensor * 2% OR |actual-sensor| ≤ 1000"; } identity accuracy-measured-ones { base accuracy-measured; diff --git a/experimental/ietf-extracted-YANG-modules/ietf-schc-coap@2025-12-01.yang b/experimental/ietf-extracted-YANG-modules/ietf-schc-coap@2026-06-03.yang similarity index 97% rename from experimental/ietf-extracted-YANG-modules/ietf-schc-coap@2025-12-01.yang rename to experimental/ietf-extracted-YANG-modules/ietf-schc-coap@2026-06-03.yang index 8ef59d666..dd3bbe191 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-schc-coap@2025-12-01.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-schc-coap@2026-06-03.yang @@ -36,7 +36,7 @@ module ietf-schc-coap { This module extends the ietf-schc module defined in RFC 9363 to include the new CoAP options as defined in RFC YYYY."; - revision 2025-12-01 { + revision 2026-06-03 { description "New CoAP extensions and extended OSCORE fields."; reference @@ -126,7 +126,7 @@ module ietf-schc-coap { identity fl-oscore-oscore-piv-length { base "schc:fl-base-type"; description - "Size in bytes of the OSCORE Partial IV corresponding to n."; + "Size in bytes of the OSCORE Partial IV, equal to n."; reference "RFC YYYY Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP) (see diff --git a/standard/ietf/RFC/ietf-inet-types@2025-12-22.yang b/standard/ietf/RFC/ietf-inet-types@2025-12-22.yang index e56e67df3..38c4971b8 100644 --- a/standard/ietf/RFC/ietf-inet-types@2025-12-22.yang +++ b/standard/ietf/RFC/ietf-inet-types@2025-12-22.yang @@ -8,7 +8,7 @@ module ietf-inet-types { "WG Web: WG List: - Editor: Jürgen Schönwälder + Editor: Jürgen Schönwälder "; description "This module contains a collection of generally useful derived diff --git a/standard/ietf/RFC/ietf-yang-types@2025-12-22.yang b/standard/ietf/RFC/ietf-yang-types@2025-12-22.yang index 09218bbd4..0ba3b341e 100644 --- a/standard/ietf/RFC/ietf-yang-types@2025-12-22.yang +++ b/standard/ietf/RFC/ietf-yang-types@2025-12-22.yang @@ -8,7 +8,7 @@ module ietf-yang-types { "WG Web: WG List: - Editor: Jürgen Schönwälder + Editor: Jürgen Schönwälder "; description "This module contains a collection of generally useful derived