From 92189acfdefea0347183ee17fbb26570681e042d Mon Sep 17 00:00:00 2001 From: Joe Clarke Date: Mon, 30 Sep 2024 06:29:20 -0400 Subject: [PATCH] yc.o sync (#1587) * Cronjob - daily check of IETF modules. --------- Co-authored-by: Miroslav Kovac --- ...04.yang => iana-bfd-types@2024-09-23.yang} | 9 +- ...yang => ietf-bfd-opt-auth@2024-09-23.yang} | 37 +- .../ietf-syslog@2024-03-21.yang | 931 ----------------- .../ietf-syslog@2024-09-18.yang | 959 ++++++++++++++++++ ...g => ietf-te-packet-types@2024-09-27.yang} | 112 +- ...-23.yang => ietf-te-types@2024-09-13.yang} | 51 +- .../ietf-template@2023-07-26.yang | 3 +- standard/iana/yang-parameters.xml | 10 +- 8 files changed, 1100 insertions(+), 1012 deletions(-) rename experimental/ietf-extracted-YANG-modules/{iana-bfd-types@2024-07-04.yang => iana-bfd-types@2024-09-23.yang} (95%) rename experimental/ietf-extracted-YANG-modules/{ietf-bfd-opt-auth@2024-07-04.yang => ietf-bfd-opt-auth@2024-09-23.yang} (85%) delete mode 100644 experimental/ietf-extracted-YANG-modules/ietf-syslog@2024-03-21.yang create mode 100644 experimental/ietf-extracted-YANG-modules/ietf-syslog@2024-09-18.yang rename experimental/ietf-extracted-YANG-modules/{ietf-te-packet-types@2024-07-23.yang => ietf-te-packet-types@2024-09-27.yang} (89%) rename experimental/ietf-extracted-YANG-modules/{ietf-te-types@2024-07-23.yang => ietf-te-types@2024-09-13.yang} (99%) diff --git a/experimental/ietf-extracted-YANG-modules/iana-bfd-types@2024-07-04.yang b/experimental/ietf-extracted-YANG-modules/iana-bfd-types@2024-09-23.yang similarity index 95% rename from experimental/ietf-extracted-YANG-modules/iana-bfd-types@2024-07-04.yang rename to experimental/ietf-extracted-YANG-modules/iana-bfd-types@2024-09-23.yang index 9d7d3bdc0..fad1a0739 100644 --- a/experimental/ietf-extracted-YANG-modules/iana-bfd-types@2024-07-04.yang +++ b/experimental/ietf-extracted-YANG-modules/iana-bfd-types@2024-09-23.yang @@ -32,18 +32,17 @@ module iana-bfd-types { Relating to IETF Documents (https://trustee.ietf.org/license-info). - This version of this YANG module is part of RFC 9127; see the - RFC itself for full legal notices."; + The initial version of this YANG module is part of RFC 9127; + see the RFC itself for full legal notices."; reference "RFC 9127: YANG Data Model for Bidirectional Forwarding Detection (BFD)"; - revision 2024-07-04 { + revision 2024-09-23 { description "Add NULL and Meticulous ISAAC authentication type."; reference - "I-D.ietf-bfd-optimizing-authentication: - Optimizing BFD Authentication, + "RFC XXXX: Optimizing BFD Authentication, I-D.ietf-bfd-stability: BFD Stability."; } diff --git a/experimental/ietf-extracted-YANG-modules/ietf-bfd-opt-auth@2024-07-04.yang b/experimental/ietf-extracted-YANG-modules/ietf-bfd-opt-auth@2024-09-23.yang similarity index 85% rename from experimental/ietf-extracted-YANG-modules/ietf-bfd-opt-auth@2024-07-04.yang rename to experimental/ietf-extracted-YANG-modules/ietf-bfd-opt-auth@2024-09-23.yang index 25b6ac9e8..9313172ef 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-bfd-opt-auth@2024-07-04.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-bfd-opt-auth@2024-09-23.yang @@ -14,41 +14,41 @@ module ietf-bfd-opt-auth { prefix bfd; reference "RFC 9314: YANG Data Model for Bidirectional - Forwarding Detection."; + Forwarding Detection (BFD)."; } import ietf-bfd-ip-sh { prefix bfd-ip-sh; reference "RFC 9314: YANG Data Model for Bidirectional - Forwarding Detection."; + Forwarding Detection (BFD)."; } import ietf-bfd-ip-mh { prefix bfd-ip-mh; reference "RFC 9314: YANG Data Model for Bidirectional - Forwarding Detection."; + Forwarding Detection (BFD)."; } import ietf-bfd-lag { prefix bfd-lag; reference "RFC 9314: YANG Data Model for Bidirectional - Forwarding Detection."; + Forwarding Detection (BFD)."; } import ietf-bfd-mpls { prefix bfd-mpls; reference "RFC 9314: YANG Data Model for Bidirectional - Forwarding Detection."; + Forwarding Detection (BFD)."; } import ietf-key-chain { prefix key-chain; reference - "RFC 8177: YANG Key Chain."; + "RFC 8177: YANG Data Model for Key Chains."; } organization @@ -87,7 +87,7 @@ module ietf-bfd-opt-auth { described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here."; - revision "2024-07-04" { + revision "2024-09-23" { description "Initial Version."; reference @@ -107,8 +107,7 @@ module ietf-bfd-opt-auth { strong authentication and Meticulous Keyed ISAAC Keyed as the 'optimized' authentication."; reference - "I-D.ietf-bfd-optimizing-authentication: - Meticulous Keyed ISAAC for BFD Authentication. + "RFC XXXX: Meticulous Keyed ISAAC for BFD Authentication. I-D.ietf-bfd-secure-sequence-numbers: Meticulous Keyed ISAAC for BFD Authentication."; } @@ -154,8 +153,9 @@ module ietf-bfd-opt-auth { uses bfd-opt-auth-config; description - "Augment the 'authentication' container in BFD module to - add attributes related to BFD optimized authentication."; + "Augment the 'authentication' container for single hop BFD + module to add attributes related to BFD optimized + authentication."; } augment "/rt:routing/rt:control-plane-protocols/" + @@ -165,8 +165,9 @@ module ietf-bfd-opt-auth { uses bfd-opt-auth-config; description - "Augment the 'authentication' container in BFD module to - add attributes related to BFD optimized authentication."; + "Augment the 'authentication' container for multi-hop BFD + module to add attributes related to BFD optimized + authentication."; } augment "/rt:routing/rt:control-plane-protocols/" + @@ -176,8 +177,9 @@ module ietf-bfd-opt-auth { uses bfd-opt-auth-config; description - "Augment the 'authentication' container in BFD module to - add attributes related to BFD optimized authentication."; + "Augment the 'authentication' container for BFD over LAG + module to add attributes related to BFD optimized + authentication."; } augment "/rt:routing/rt:control-plane-protocols/" + @@ -187,7 +189,8 @@ module ietf-bfd-opt-auth { uses bfd-opt-auth-config; description - "Augment the 'authentication' container in BFD module to - add attributes related to BFD optimized authentication."; + "Augment the 'authentication' container for BFD over MPLS + module to add attributes related to BFD optimized + authentication."; } } diff --git a/experimental/ietf-extracted-YANG-modules/ietf-syslog@2024-03-21.yang b/experimental/ietf-extracted-YANG-modules/ietf-syslog@2024-03-21.yang deleted file mode 100644 index e33c559a4..000000000 --- a/experimental/ietf-extracted-YANG-modules/ietf-syslog@2024-03-21.yang +++ /dev/null @@ -1,931 +0,0 @@ -module ietf-syslog { - yang-version 1.1; - namespace "urn:ietf:params:xml:ns:yang:ietf-syslog"; - prefix syslog; - - import ietf-inet-types { - prefix inet; - reference - "RFC 6991: Common YANG Data Types"; - } - import ietf-interfaces { - prefix if; - reference - "RFC 8343: A YANG Data Model for Interface Management"; - } - import ietf-tls-client { - prefix tlsc; - reference - "I-D.ietf-netconf-tls-client-server: - YANG Groupings for TLS Clients and TLS Servers"; - } - import ietf-crypto-types { - prefix ct; - reference - "I-D.ietf-netconf-crypto-types: YANG Data Types for - Cryptography"; - } - - organization - "IETF NETMOD (Network Modeling) Working Group"; - contact - "WG Web: - WG List: - - Editor: Mahesh Jethanandani - - - Editor: Joe Clarke - - - Editor: Kiran Agrahara Sreenivasa - - - Editor: Clyde Wildes - "; - description - "This module contains a collection of YANG definitions - for syslog configuration. - - 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 zzzz - (https://www.rfc-editor.org/info/rfczzzz); - 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 2024-03-21 { - description - "Initial Revision"; - reference - "RFC zzzz: Syslog YANG Model"; - } - - feature console-action { - description - "This feature indicates that the local console action is - supported."; - } - - feature file-action { - description - "This feature indicates that the local file action is - supported."; - } - - feature file-limit-size { - description - "This feature indicates that file logging resources - are managed using size and number limits."; - } - - feature file-limit-duration { - description - "This feature indicates that file logging resources - are managed using time based limits."; - } - - feature remote-action { - description - "This feature indicates that the remote server action is - supported."; - } - - feature remote-source-interface { - description - "This feature indicates that source-interface is supported - supported for the remote-action."; - } - - feature select-adv-compare { - description - "This feature represents the ability to select messages - using the additional comparison operators when comparing - the syslog message severity."; - } - - feature select-match { - description - "This feature represents the ability to select messages - based on a Posix 1003.2 regular expression pattern - match."; - } - - feature structured-data { - description - "This feature represents the ability to log messages - in structured-data format."; - reference - "RFC 5424: The Syslog Protocol"; - } - - feature signed-messages { - description - "This feature represents the ability to configure signed - syslog messages."; - reference - "RFC 5848: Signed Syslog Messages"; - } - - typedef syslog-severity { - type enumeration { - enum emergency { - value 0; - description - "The severity level 'Emergency' indicating that the - system is unusable."; - } - enum alert { - value 1; - description - "The severity level 'Alert' indicating that an - action must be taken immediately."; - } - enum critical { - value 2; - description - "The severity level 'Critical' indicating a - critical condition."; - } - enum error { - value 3; - description - "The severity level 'Error' indicating an error - condition."; - } - enum warning { - value 4; - description - "The severity level 'Warning' indicating a warning - condition."; - } - enum notice { - value 5; - description - "The severity level 'Notice' indicating a normal - but significant condition."; - } - enum info { - value 6; - description - "The severity level 'Info' indicating an - informational message."; - } - enum debug { - value 7; - description - "The severity level 'Debug' indicating a - debug-level message."; - } - } - description - "The definitions for Syslog message severity. - Note that a lower value is a higher severity. Comparisons - of equal-or-higher severity mean equal or lower numeric - value"; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity syslog-facility { - description - "This identity is used as a base for all syslog - facilities."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity kern { - base syslog-facility; - description - "The facility for kernel messages (0)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity user { - base syslog-facility; - description - "The facility for user-level messages (1)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity mail { - base syslog-facility; - description - "The facility for the mail system (2)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity daemon { - base syslog-facility; - description - "The facility for the system daemons (3)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity auth { - base syslog-facility; - description - "The facility for security/authorization messages (4)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity syslog { - base syslog-facility; - description - "The facility for messages generated internally by syslogd - facility (5)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity lpr { - base syslog-facility; - description - "The facility for the line printer subsystem (6)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity news { - base syslog-facility; - description - "The facility for the network news subsystem (7)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity uucp { - base syslog-facility; - description - "The facility for the UUCP subsystem (8)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity cron { - base syslog-facility; - description - "The facility for the clock daemon (9)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity authpriv { - base syslog-facility; - description - "The facility for privileged security/authorization - messages (10)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity ftp { - base syslog-facility; - description - "The facility for the FTP daemon (11)."; - reference - "RFC 5424: The Syslog Protocol"; - } - identity ntp { - base syslog-facility; - description - "The facility for the NTP subsystem (12)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity audit { - base syslog-facility; - description - "The facility for log audit messages (13)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity console { - base syslog-facility; - description - "The facility for log alert messages (14)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity cron2 { - base syslog-facility; - description - "The facility for the second clock daemon (15)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity local0 { - base syslog-facility; - description - "The facility for local use 0 messages (16)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity local1 { - base syslog-facility; - description - "The facility for local use 1 messages (17)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity local2 { - base syslog-facility; - description - "The facility for local use 2 messages (18)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity local3 { - base syslog-facility; - description - "The facility for local use 3 messages (19)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity local4 { - base syslog-facility; - description - "The facility for local use 4 messages (20)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity local5 { - base syslog-facility; - description - "The facility for local use 5 messages (21)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity local6 { - base syslog-facility; - description - "The facility for local use 6 messages (22)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity local7 { - base syslog-facility; - description - "The facility for local use 7 messages (23)."; - reference - "RFC 5424: The Syslog Protocol"; - } - - identity action { - description - "Base identity for action for how a message will be - handled."; - } - - identity log { - base action; - description - "This identity specifies that if the compare operation is - true the message will be logged."; - } - - identity block { - base action; - description - "This identity specifies that if the compare operation is - true the message will not be logged."; - } - - identity stop { - base action; - description - "This identity specifies that if the compare operation is - true the message will not be logged and no further - processing will occur for it."; - } - - grouping severity-filter { - description - "This grouping defines the processing used to select - log messages by comparing syslog message severity using - the following processing rules: - - if 'none', do not match. - - if 'all', match. - - else compare message severity with the specified - severity according to the default compare rule (all - messages of the specified severity and greater match) - or if the select-adv-compare feature is present, use - the advance-compare rule."; - leaf severity { - type union { - type syslog-severity; - type enumeration { - enum none { - value 2147483647; - description - "This enum describes the case where no - severities are selected."; - } - enum all { - value -2147483648; - description - "This enum describes the case where all - severities are selected."; - } - } - } - mandatory true; - description - "This leaf specifies the syslog message severity."; - } - container advanced-compare { - when "../severity != \"all\" and - ../severity != \"none\"" { - description - "The advanced compare container is not applicable - for severity 'all' or severity 'none'"; - } - if-feature "select-adv-compare"; - leaf compare { - type enumeration { - enum equals { - description - "This enum specifies that the severity - comparison operation will be equals."; - } - enum equals-or-higher { - description - "This enum specifies that the severity - comparison operation will be equals or - higher."; - } - } - default "equals-or-higher"; - description - "The compare can be used to specify the comparison - operator that should be used to compare the syslog - message severity with the specified severity."; - } - leaf action { - type identityref { - base "action"; - } - default "log"; - description - "The action can be used to specify how the message - should be handled. This may include logging the - message, not logging the message (i.e., blocking - it), or stopping further processing."; - } - description - "This container describes additional severity compare - operations that can be used in place of the default - severity comparison. The compare leaf specifies the - type of the compare that is done and the action leaf - specifies the intended result. - Example: compare->equals and action->block means - messages that have a severity that are equal to the - specified severity will not be logged."; - } - } - - grouping selector { - description - "This grouping defines a syslog selector which is used to - select log messages for the log-actions (console, file, - remote, etc.). Choose one or both of the following: - facility [ ...] - pattern-match regular-expression-match-string - If both facility and pattern-match are specified, both - must match in order for a log message to be selected."; - container facility-filter { - description - "This container describes the syslog filter - parameters."; - list facility-list { - key "facility severity"; - ordered-by user; - description - "This list describes a collection of syslog - facilities and severities."; - leaf facility { - type union { - type identityref { - base syslog-facility; - } - type enumeration { - enum all { - description - "This enum describes the case where - all facilities are requested."; - } - } - } - description - "The leaf uniquely identifies a syslog - facility."; - } - uses severity-filter; - } - } - leaf pattern-match { - if-feature "select-match"; - type string; - description - "This leaf describes a Posix 1003.2 regular expression - string that can be used to select a syslog message for - logging. The match is performed on the SYSLOG-MSG - field."; - reference - "RFC 5424: The Syslog Protocol - Std-1003.1-2008 Regular Expressions"; - } - } - - grouping structured-data { - description - "This grouping defines the syslog structured data option - which is used to select the format used to write log - messages."; - leaf structured-data { - if-feature "structured-data"; - type boolean; - default "false"; - description - "This leaf describes how log messages are written. - If true, messages will be written with one or more - STRUCTURED-DATA elements; if false, messages will be - written with STRUCTURED-DATA = NILVALUE."; - reference - "RFC 5424: The Syslog Protocol"; - } - } - - container syslog { - presence - "Enables logging."; - description - "This container describes the configuration parameters for - syslog."; - container actions { - description - "This container describes the log-action parameters - for syslog."; - container console { - if-feature "console-action"; - presence - "Enables logging to the console"; - description - "This container describes the configuration - parameters for console logging."; - uses selector; - } - container file { - if-feature "file-action"; - description - "This container describes the configuration - parameters for file logging. If file-archive - limits are not supplied, it is assumed that - the local implementation defined limits will - be used."; - list log-file { - key "name"; - description - "This list describes a collection of local - logging files."; - leaf name { - type inet:uri { - pattern - 'file:.*'; - } - description - "This leaf specifies the name of the log - file which MUST use the uri scheme - file:."; - reference - "RFC 8089: The file URI Scheme"; - } - uses selector; - uses structured-data; - container file-rotation { - description - "This container describes the configuration - parameters for log file rotation."; - leaf number-of-files { - if-feature "file-limit-size"; - type uint32; - default "1"; - description - "This leaf specifies the maximum number - of log files retained. Specify 1 for - implementations that only support one - log file."; - } - leaf max-file-size { - if-feature "file-limit-size"; - type uint32; - units "megabytes"; - description - "This leaf specifies the maximum log - file size."; - } - leaf rollover { - if-feature "file-limit-duration"; - type uint32; - units "minutes"; - description - "This leaf specifies the length of time - that log events should be written to a - specific log file. Log events that - arrive after the rollover period cause - the current log file to be closed and - a new log file to be opened."; - } - leaf retention { - if-feature "file-limit-duration"; - type uint32; - units "minutes"; - description - "This leaf specifies the length of time - that completed/closed log event files - should be stored in the file system - before they are removed."; - } - } - } - } - container remote { - if-feature "remote-action"; - description - "This container describes the configuration - parameters for forwarding syslog messages - to remote relays or collectors."; - list destination { - key "name"; - description - "This list describes a collection of remote - logging destinations."; - leaf name { - type string; - description - "An arbitrary name for the endpoint to - connect to."; - } - choice transport { - mandatory true; - description - "This choice describes the transport - option."; - case udp { - container udp { - description - "This container describes the UDP - transport options."; - reference - "RFC 5426: Transmission of Syslog - Messages over UDP"; - leaf address { - type inet:host; - description - "The leaf uniquely specifies - the address of the remote - host. One of the following - must be specified: an ipv4 - address, an ipv6 address, or a - host name."; - } - leaf port { - type inet:port-number; - default "514"; - description - "This leaf specifies the port - number used to deliver - messages to the remote - server."; - } - } - } - case tls { - container tls { - description - "This container describes the TLS - transport options."; - reference - "RFC 5425: Transport Layer Security - (TLS) Transport Mapping for - Syslog "; - leaf address { - type inet:host; - description - "The leaf uniquely specifies - the address of the remote - host. One of the following - must be specified: an ipv4 - address, an ipv6 address, or - a host name."; - } - leaf port { - type inet:port-number; - default "6514"; - description - "TCP port 6514 has been - allocated as the default port - for syslog over TLS."; - } - uses tlsc:tls-client-grouping; - } - } - } - uses selector; - uses structured-data; - leaf facility-override { - type identityref { - base syslog-facility; - } - description - "If specified, this leaf specifies the - facility used to override the facility - in messages delivered to the remote - server."; - } - leaf source-interface { - if-feature "remote-source-interface"; - type if:interface-ref; - description - "This leaf sets the source interface to be - used to send messages to the remote syslog - server. If not set, messages can be sent - on any interface."; - } - container signing { - if-feature "signed-messages"; - presence - "If present, syslog-signing options is - activated."; - description - "This container describes the configuration - parameters for signed syslog messages."; - reference - "RFC 5848: Signed Syslog Messages"; - container cert-signers { - description - "This container describes the signing - certificate configuration for - Signature Group 0 which covers the - case for administrators who want all - Signature Blocks to be sent to a - single destination."; - list cert-signer { - key "name"; - description - "This list describes a collection - of syslog message signers."; - leaf name { - type string; - description - "This leaf specifies the name - of the syslog message - signer."; - } - container cert { - uses ct:asymmetric-key-pair-with-cert-grouping; - description - "This is the certificate that - is periodically sent to the - remote receiver. The - certificate is inherently - associated with its private - and public keys."; - } - leaf hash-algorithm { - type enumeration { - enum SHA1 { - value 1; - description - "This enum describes - the SHA1 algorithm."; - } - enum SHA256 { - value 2; - description - "This enum describes - the SHA256 - algorithm."; - } - } - description - "This leaf describes the syslog - signer hash algorithm used."; - } - } - leaf cert-initial-repeat { - type uint32; - default "3"; - description - "This leaf specifies the number of - times each Certificate Block - should be sent before the first - message is sent."; - } - leaf cert-resend-delay { - type uint32; - units "seconds"; - default "3600"; - description - "This leaf specifies the maximum - time delay in seconds until - resending the Certificate Block."; - } - leaf cert-resend-count { - type uint32; - default "0"; - description - "This leaf specifies the maximum - number of other syslog messages to - send until resending the - Certificate Block."; - } - leaf sig-max-delay { - type uint32; - units "seconds"; - default "60"; - description - "This leaf specifies when to - generate a new Signature Block. If - this many seconds have elapsed - since the message with the first - message number of the Signature - Block was sent, a new Signature - Block should be generated."; - } - leaf sig-number-resends { - type uint32; - default "0"; - description - "This leaf specifies the number of - times a Signature Block is resent. - (It is recommended to select a - value of greater than 0 in - particular when the UDP transport - RFC 5426 is used.)."; - } - leaf sig-resend-delay { - type uint32; - units "seconds"; - default "5"; - description - "This leaf specifies when to send - the next Signature Block - transmission based on time. If - this many seconds have elapsed - since the previous sending of this - Signature Block, resend it."; - } - leaf sig-resend-count { - type uint32; - default "0"; - description - "This leaf specifies when to send - the next Signature Block - transmission based on a count. If - this many other syslog messages - have been sent since the previous - sending of this Signature Block, - resend it. A value of 0 means that - you don't resend based on the - number of messages."; - } - } - } - } - } - } - } -} diff --git a/experimental/ietf-extracted-YANG-modules/ietf-syslog@2024-09-18.yang b/experimental/ietf-extracted-YANG-modules/ietf-syslog@2024-09-18.yang new file mode 100644 index 000000000..45e523627 --- /dev/null +++ b/experimental/ietf-extracted-YANG-modules/ietf-syslog@2024-09-18.yang @@ -0,0 +1,959 @@ +module ietf-syslog { + yang-version 1.1; + namespace "urn:ietf:params:xml:ns:yang:ietf-syslog"; + prefix syslog; + + import ietf-inet-types { + prefix inet; + reference + "RFC 6991: Common YANG Data Types"; + } + + import ietf-interfaces { + prefix if; + reference + "RFC 8343: A YANG Data Model for Interface Management"; + } + + import ietf-tls-client { + prefix tlsc; + reference + "I-D.ietf-netconf-tls-client-server: + YANG Groupings for TLS Clients and TLS Servers"; + } + + import ietf-crypto-types { + prefix ct; + reference + "I-D.ietf-netconf-crypto-types: YANG Data Types for + Cryptography"; + } + + organization + "IETF NETMOD (Network Modeling) Working Group"; + contact + "WG Web: + WG List: + + Editor: Mahesh Jethanandani + + + Editor: Joe Clarke + + + Editor: Kiran Agrahara Sreenivasa + + + Editor: Clyde Wildes + "; + description + "This module contains a collection of YANG definitions + for syslog configuration. + + 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 zzzz + (https://www.rfc-editor.org/info/rfczzzz); + 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 2024-09-18 { + description + "Initial Revision"; + reference + "RFC zzzz: Syslog YANG Model"; + } + + feature console-action { + description + "This feature indicates that the local console action is + supported."; + } + + feature file-action { + description + "This feature indicates that the local file action is + supported."; + } + + feature file-limit-size { + description + "This feature indicates that file logging resources + are managed using size and number limits."; + } + + feature file-limit-duration { + description + "This feature indicates that file logging resources + are managed using time based limits."; + } + + feature remote-action { + description + "This feature indicates that the remote server action is + supported."; + } + + feature remote-source-interface { + description + "This feature indicates that source-interface is supported + supported for the remote-action."; + } + + feature select-adv-compare { + description + "This feature represents the ability to select messages + using the additional comparison operators when comparing + the syslog message severity."; + } + + feature select-match { + description + "This feature represents the ability to select messages + based on a Posix 1003.2 regular expression pattern + match."; + } + + feature structured-data { + description + "This feature represents the ability to log messages + in structured-data format."; + reference + "RFC 5424: The Syslog Protocol"; + } + + feature signed-messages { + description + "This feature represents the ability to configure signed + syslog messages."; + reference + "RFC 5848: Signed Syslog Messages"; + } + + typedef syslog-severity { + type enumeration { + enum emergency { + value 0; + description + "The severity level 'Emergency' indicating that the + system is unusable."; + } + enum alert { + value 1; + description + "The severity level 'Alert' indicating that an + action must be taken immediately."; + } + enum critical { + value 2; + description + "The severity level 'Critical' indicating a + critical condition."; + } + enum error { + value 3; + description + "The severity level 'Error' indicating an error + condition."; + } + enum warning { + value 4; + description + "The severity level 'Warning' indicating a warning + condition."; + } + enum notice { + value 5; + description + "The severity level 'Notice' indicating a normal + but significant condition."; + } + enum info { + value 6; + description + "The severity level 'Info' indicating an + informational message."; + } + enum debug { + value 7; + description + "The severity level 'Debug' indicating a + debug-level message."; + } + } + description + "The definitions for Syslog message severity. + Note that a lower value is a higher severity. Comparisons + of equal-or-higher severity mean equal or lower numeric + value"; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity syslog-facility { + description + "This identity is used as a base for all syslog + facilities."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity kern { + base syslog-facility; + description + "The facility for kernel messages (0)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity user { + base syslog-facility; + description + "The facility for user-level messages (1)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity mail { + base syslog-facility; + description + "The facility for the mail system (2)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity daemon { + base syslog-facility; + description + "The facility for the system daemons (3)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity auth { + base syslog-facility; + description + "The facility for security/authorization messages (4)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity syslog { + base syslog-facility; + description + "The facility for messages generated internally by syslogd + facility (5)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity lpr { + base syslog-facility; + description + "The facility for the line printer subsystem (6)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity news { + base syslog-facility; + description + "The facility for the network news subsystem (7)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity uucp { + base syslog-facility; + description + "The facility for the UUCP subsystem (8)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity cron { + base syslog-facility; + description + "The facility for the clock daemon (9)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity authpriv { + base syslog-facility; + description + "The facility for privileged security/authorization + messages (10)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity ftp { + base syslog-facility; + description + "The facility for the FTP daemon (11)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity ntp { + base syslog-facility; + description + "The facility for the NTP subsystem (12)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity audit { + base syslog-facility; + description + "The facility for log audit messages (13)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity console { + base syslog-facility; + description + "The facility for log alert messages (14)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity cron2 { + base syslog-facility; + description + "The facility for the second clock daemon (15)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity local0 { + base syslog-facility; + description + "The facility for local use 0 messages (16)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity local1 { + base syslog-facility; + description + "The facility for local use 1 messages (17)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity local2 { + base syslog-facility; + description + "The facility for local use 2 messages (18)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity local3 { + base syslog-facility; + description + "The facility for local use 3 messages (19)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity local4 { + base syslog-facility; + description + "The facility for local use 4 messages (20)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity local5 { + base syslog-facility; + description + "The facility for local use 5 messages (21)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity local6 { + base syslog-facility; + description + "The facility for local use 6 messages (22)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity local7 { + base syslog-facility; + description + "The facility for local use 7 messages (23)."; + reference + "RFC 5424: The Syslog Protocol"; + } + + identity action { + description + "Base identity for action for how a message will be + handled."; + } + + identity log { + base action; + description + "This identity specifies that if the compare operation is + true the message will be logged."; + } + + identity block { + base action; + description + "This identity specifies that if the compare operation is + true the message will not be logged."; + } + + identity stop { + base action; + description + "This identity specifies that if the compare operation is + true the message will not be logged and no further + processing will occur for it."; + } + + grouping severity-filter { + description + "This grouping defines the processing used to select + log messages by comparing syslog message severity using + the following processing rules: + - if 'none', do not match. + - if 'all', match. + - else compare message severity with the specified + severity according to the default compare rule (all + messages of the specified severity and greater match) + or if the select-adv-compare feature is present, use + the advance-compare rule."; + + leaf severity { + type union { + type syslog-severity; + type enumeration { + enum none { + value 2147483647; + description + "This enum describes the case where no + severities are selected."; + } + enum all { + value -2147483648; + description + "This enum describes the case where all + severities are selected."; + } + } + } + mandatory true; + description + "This leaf specifies the syslog message severity."; + } + + container advanced-compare { + when "../severity != \"all\" and + ../severity != \"none\"" { + description + "The advanced compare container is not applicable + for severity 'all' or severity 'none'"; + } + if-feature "select-adv-compare"; + + leaf compare { + type enumeration { + enum equals { + description + "This enum specifies that the severity + comparison operation will be equals."; + } + enum equals-or-higher { + description + "This enum specifies that the severity + comparison operation will be equals or + higher."; + } + } + default "equals-or-higher"; + description + "The compare can be used to specify the comparison + operator that should be used to compare the syslog + message severity with the specified severity."; + } + + leaf action { + type identityref { + base "action"; + } + default "log"; + description + "The action can be used to specify how the message + should be handled. This may include logging the + message, not logging the message (i.e., blocking + it), or stopping further processing."; + } + description + "This container describes additional severity compare + operations that can be used in place of the default + severity comparison. The compare leaf specifies the + type of the compare that is done and the action leaf + specifies the intended result. + Example: compare->equals and action->block means + messages that have a severity that are equal to the + specified severity will not be logged."; + } + } + + grouping selector { + description + "This grouping defines a syslog selector which is used to + select log messages for the log-actions (console, file, + remote, etc.). Choose one or both of the following: + facility [ ...] + pattern-match regular-expression-match-string + If both facility and pattern-match are specified, both + must match in order for a log message to be selected."; + + container filter { + description + "This container describes the syslog filter + parameters."; + + list facility-list { + key "facility severity"; + ordered-by user; + description + "This list describes a collection of syslog + facilities and severities."; + + leaf facility { + type union { + type identityref { + base syslog-facility; + } + type enumeration { + enum all { + description + "This enum describes the case where + all facilities are requested."; + } + } + } + description + "The leaf uniquely identifies a syslog + facility."; + } + uses severity-filter; + } + } + + leaf pattern-match { + if-feature "select-match"; + type string; + description + "This leaf describes a Posix 1003.2 regular expression + string that can be used to select a syslog message for + logging. The match is performed on the SYSLOG-MSG + field."; + reference + "RFC 5424: The Syslog Protocol + Std-1003.1-2008 Regular Expressions"; + } + } + + grouping structured-data { + description + "This grouping defines the syslog structured data option + which is used to select the format used to write log + messages."; + + leaf structured-data { + if-feature "structured-data"; + type boolean; + default "false"; + description + "This leaf describes how log messages are written. + If true, messages will be written with one or more + STRUCTURED-DATA elements; if false, messages will be + written with STRUCTURED-DATA = NILVALUE."; + reference + "RFC 5424: The Syslog Protocol"; + } + } + + container syslog { + presence + "Enables logging."; + description + "This container describes the configuration parameters for + syslog."; + + container actions { + description + "This container describes the log-action parameters + for syslog."; + + container console { + if-feature "console-action"; + presence + "Enables logging to the console"; + description + "This container describes the configuration + parameters for console logging."; + uses selector; + } + + container file { + if-feature "file-action"; + description + "This container describes the configuration + parameters for file logging. If file-archive + limits are not supplied, it is assumed that + the local implementation defined limits will + be used."; + + list log-file { + key "name"; + description + "This list describes a collection of local + logging files."; + + leaf name { + type inet:uri { + pattern + 'file:.*'; + } + description + "This leaf specifies the name of the log + file which MUST use the uri scheme + file:."; + reference + "RFC 8089: The file URI Scheme"; + } + + uses selector; + uses structured-data; + + container file-rotation { + description + "This container describes the configuration + parameters for log file rotation."; + leaf number-of-files { + if-feature "file-limit-size"; + type uint32; + default "1"; + description + "This leaf specifies the maximum number + of log files retained. Specify 1 for + implementations that only support one + log file."; + } + + leaf max-file-size { + if-feature "file-limit-size"; + type uint32; + units "megabytes"; + description + "This leaf specifies the maximum log + file size."; + } + + leaf rollover { + if-feature "file-limit-duration"; + type uint32; + units "minutes"; + description + "This leaf specifies the length of time + that log events should be written to a + specific log file. Log events that + arrive after the rollover period cause + the current log file to be closed and + a new log file to be opened."; + } + + leaf retention { + if-feature "file-limit-duration"; + type uint32; + units "minutes"; + description + "This leaf specifies the length of time + that completed/closed log event files + should be stored in the file system + before they are removed."; + } + } + } + } + + container remote { + if-feature "remote-action"; + description + "This container describes the configuration + parameters for forwarding syslog messages + to remote relays or collectors."; + + list destination { + key "name"; + description + "This list describes a collection of remote logging + destinations."; + leaf name { + type string; + description + "An arbitrary name for the endpoint to connect to."; + } + + choice transport { + mandatory true; + description + "This choice describes the transport option."; + + case udp { + container udp { + description + "This container describes the UDP transport + options."; + reference + "RFC 5426: Transmission of Syslog Messages over + UDP"; + + list udp { + key "address"; + description + "List of all UDP sessions."; + + leaf address { + type inet:host; + description + "The leaf uniquely specifies the address of the + remote host. One of the following must be + specified: + - an ipv4 address, + - an ipv6 address, or a + - host name."; + } + + leaf port { + type inet:port-number; + default "514"; + description + "This leaf specifies the port number used to + deliver messages to the remote server."; + } + } + } + } + + case tls { + container tls { + description + "This container describes the TLS transport + options."; + reference + "RFC 5425: Transport Layer Security (TLS) Transport + Mapping for Syslog "; + + list tls { + key "address"; + description + "List of all TLS based sessions."; + + leaf address { + type inet:host; + description + "The leaf uniquely specifies the address of the + remote host. One of the following must be + specified: an ipv4 address, an ipv6 address, or + a host name."; + } + + leaf port { + type inet:port-number; + default "6514"; + description + "TCP port 6514 has been allocated as the + default port for syslog over TLS."; + } + uses tlsc:tls-client-grouping; + } + } + } + } + + uses selector; + uses structured-data; + + leaf facility-override { + type identityref { + base syslog-facility; + } + description + "If specified, this leaf specifies the facility used + to override the facility in messages delivered to the + remote server."; + } + + leaf source-interface { + if-feature "remote-source-interface"; + type if:interface-ref; + description + "This leaf sets the source interface to be used to + send messages to the remote syslog server. If not set, + messages can be sent on any interface."; + } + + container signing { + if-feature "signed-messages"; + presence + "If present, syslog-signing options is activated."; + description + "This container describes the configuration + parameters for signed syslog messages."; + reference + "RFC 5848: Signed Syslog Messages"; + + container cert-signers { + description + "This container describes the signing certificate + configuration for Signature Group 0 which covers the + case for administrators who want all Signature + Blocks to be sent to a single destination."; + + list cert-signer { + key "name"; + description + "This list describes a collection of syslog message + signers."; + + leaf name { + type string; + description + "This leaf specifies the name of the syslog + message signer."; + } + + container cert { + uses ct:asymmetric-key-pair-with-cert-grouping; + description + "This is the certificate that is periodically + sent to the remote receiver. The certificate is + inherently associated with its private + and public keys."; + } + + leaf hash-algorithm { + type enumeration { + enum SHA1 { + value 1; + description + "This enum describes the SHA1 algorithm."; + } + enum SHA256 { + value 2; + description + "This enum describes the SHA256 algorithm."; + } + } + description + "This leaf describes the syslog signer hash + algorithm used."; + } + } + + leaf cert-initial-repeat { + type uint32; + default "3"; + description + "This leaf specifies the number of times each + Certificate Block should be sent before the first + message is sent."; + } + + leaf cert-resend-delay { + type uint32; + units "seconds"; + default "3600"; + description + "This leaf specifies the maximum time delay in + seconds until resending the Certificate Block."; + } + + leaf cert-resend-count { + type uint32; + default "0"; + description + "This leaf specifies the maximum number of other + syslog messages to send until resending the + Certificate Block."; + } + + leaf sig-max-delay { + type uint32; + units "seconds"; + default "60"; + description + "This leaf specifies when to generate a new + Signature Block. If this many seconds have elapsed + since the message with the first message number + of the Signature Block was sent, a new Signature + Block should be generated."; + } + + leaf sig-number-resends { + type uint32; + default "0"; + description + "This leaf specifies the number of times a + Signature Block is resent. (It is recommended to + select a value of greater than 0 in particular + when the UDP transport RFC 5426 is used.)."; + } + + leaf sig-resend-delay { + type uint32; + units "seconds"; + default "5"; + description + "This leaf specifies when to send the next + Signature Block transmission based on time. If + this many seconds have elapsed since the previous + sending of this Signature Block, resend it."; + } + + leaf sig-resend-count { + type uint32; + default "0"; + description + "This leaf specifies when to send the next + Signature Block transmission based on a count. If + this many other syslog messages have been sent + since the previous sending of this Signature + Block, resend it. A value of 0 means that you + don't resend based on the number of messages."; + } + } + } + } + } + } + } +} diff --git a/experimental/ietf-extracted-YANG-modules/ietf-te-packet-types@2024-07-23.yang b/experimental/ietf-extracted-YANG-modules/ietf-te-packet-types@2024-09-27.yang similarity index 89% rename from experimental/ietf-extracted-YANG-modules/ietf-te-packet-types@2024-07-23.yang rename to experimental/ietf-extracted-YANG-modules/ietf-te-packet-types@2024-09-27.yang index 62c042855..82334d35b 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-te-packet-types@2024-07-23.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-te-packet-types@2024-09-27.yang @@ -65,7 +65,7 @@ module ietf-te-packet-types { 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 2024-07-23 { + revision 2024-09-27 { description "This revision adds the following new identities: - bandwidth-profile-type; @@ -75,9 +75,9 @@ module ietf-te-packet-types { - path-metric-loss. This revision adds the following new groupings: + - bandwidth-profile-parameters; - te-packet-path-bandwidth; - te-packet-link-bandwidth. - This revision provides also few editorial changes."; reference "RFC XXXX: Common YANG Data Types for Traffic Engineering"; @@ -153,6 +153,7 @@ module ietf-te-packet-types { RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions, Section 4.3"; } + // CHANGE NOTE: The identity link-metric-loss below has // been added in this module revision // RFC Editor: remove the note above and this note @@ -203,9 +204,13 @@ module ietf-te-packet-types { typedef te-bandwidth-requested-type { type enumeration { - enum specified { + enum specified-value { + description + "Bandwidth value is explicitly specified."; + } + enum specified-profile { description - "Bandwidth is explicitly specified."; + "Bandwidth profile is explicitly specified."; } enum auto { description @@ -708,35 +713,22 @@ module ietf-te-packet-types { } } - // CHANGE NOTE: The te-packet-path-bandwidth below has been + // CHANGE NOTE: The bandwidth-profile-parameters below has been // added in this module revision // RFC Editor: remove the note above and this note - grouping te-packet-path-bandwidth { + grouping bandwidth-profile-parameters { description - "Path bandwidth for Packet. "; - leaf bandwidth-profile-name { - type string; - description - "Name of Bandwidth Profile."; - } - leaf bandwidth-profile-type { - type identityref { - base bandwidth-profile-type; - } - description - "Type of Bandwidth Profile."; - } + "Common parameters to define bandwidth profiles in packet + networks."; leaf cir { type uint64; units "bits/second"; - mandatory true; description "Committed Information Rate (CIR)."; } leaf cbs { type uint64; - units "bits/second"; - mandatory true; + units "bytes"; description "Committed Burst Size (CBS)."; } @@ -766,17 +758,89 @@ module ietf-te-packet-types { } } + // CHANGE NOTE: The te-packet-path-bandwidth below has been + // added in this module revision + // RFC Editor: remove the note above and this note + grouping te-packet-path-bandwidth { + description + "Bandwidth attributes for TE Packet paths."; + container packet-bandwidth { + description + "Bandwidth attributes for TE Packet paths."; + leaf specification-type { + type te-bandwidth-requested-type; + description + "The bandwidth specification type, either explicitly + specified or automatically computed."; + } + leaf set-bandwidth { + when "../specification-type = 'specified-value'" { + description + "When the bandwidth value is explicitly specified."; + } + type bandwidth-kbps; + description + "Set the bandwidth value explicitly, e.g., using offline + calculation."; + } + container bandwidth-profile { + when "../specification-type = 'specified-profile'" { + description + "When the bandwidth profile is explicitly specified."; + } + description + "Set the bandwidth profile attributes explicitly."; + leaf bandwidth-profile-name { + type string; + description + "Name of Bandwidth Profile."; + } + leaf bandwidth-profile-type { + type identityref { + base bandwidth-profile-type; + } + description + "Type of Bandwidth Profile."; + } + uses bandwidth-profile-parameters; + } + leaf class-type { + type te-types:te-ds-class; + description + "The Class-Type of traffic transported by the LSP."; + reference + "RFC 4124: Protocol Extensions for Support of + Diffserv-aware MPLS Traffic Engineering, + Section 4.3.1"; + } + leaf signaled-bandwidth { + type te-packet-types:bandwidth-kbps; + config false; + description + "The currently signaled bandwidth of the LSP. + + In the case where the bandwidth is specified + explicitly, then this will match the value of the + set-bandwidth leaf. + + In the cases where the bandwidth is dynamically + computed by the system, the current value of the + bandwidth should be reflected."; + } + } + } + // CHANGE NOTE: The te-packet-path-bandwidth below has been // added in this module revision // RFC Editor: remove the note above and this note grouping te-packet-link-bandwidth { description - "Link Bandwidth for Packet. "; + "Bandwidth attributes for Packet TE links."; leaf packet-bandwidth { type uint64; units "bits/second"; description - "Available bandwith value."; + "Bandwidth value for Packet TE links."; } } } diff --git a/experimental/ietf-extracted-YANG-modules/ietf-te-types@2024-07-23.yang b/experimental/ietf-extracted-YANG-modules/ietf-te-types@2024-09-13.yang similarity index 99% rename from experimental/ietf-extracted-YANG-modules/ietf-te-types@2024-07-23.yang rename to experimental/ietf-extracted-YANG-modules/ietf-te-types@2024-09-13.yang index e4430be7c..696cc0995 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-te-types@2024-07-23.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-te-types@2024-09-13.yang @@ -77,7 +77,7 @@ module ietf-te-types { 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 2024-07-23 { + revision 2024-09-13 { description "This revision adds the following new identities: - lsp-provisioning-error-reason; @@ -94,8 +94,7 @@ module ietf-te-types { - svec-metric-type and its derived identities. This revision adds the following new data types: - - path-type; - - te-gen-node-id. + - path-type. This revision adds the following new groupings: - encoding-and-switching-type; @@ -468,6 +467,7 @@ module ietf-te-types { The identifier is represented either as 4 octets in dotted-quad notation, or as 16 octets in full, mixed, shortened, or shortened-mixed IPv6 address notation. + This attribute MAY be mapped to the Router Address TLV described in Section 2.4.1 of RFC 3630, the TE Router ID described in Section 3 of RFC 6827, the Traffic Engineering @@ -660,6 +660,7 @@ module ietf-te-types { Version 2 RFC 5305: IS-IS Extensions for Traffic Engineering"; } + // CHANGE NOTE: The typedef path-type below has been // added in this module revision // RFC Editor: remove the note above and this note @@ -688,19 +689,6 @@ module ietf-te-types { path."; } - // CHANGE NOTE: The typedef te-gen-node-id below has been - // added in this module revision - // RFC Editor: remove the note above and this note - typedef te-gen-node-id { - type union { - type te-node-id; - type inet:ip-address; - type nw:node-id; - } - description - "Generic type that identifies a node in a TE topology."; - } - /* TE features */ feature p2mp-te { @@ -1120,7 +1108,6 @@ module ietf-te-types { Recovery RFC 6780: RSVP ASSOCIATION Object Extensions"; } - identity association-type-resource-sharing { base association-type; description @@ -1313,7 +1300,6 @@ module ietf-te-types { RFC 9522: Overview and Principles of Internet Traffic Engineering"; } - identity lsp-metric-type { description "Base identity for the LSP metric specification types."; @@ -1458,7 +1444,6 @@ module ietf-te-types { description "Base identity for TE tunnel states."; } - identity tunnel-state-up { base tunnel-state-type; description @@ -1668,6 +1653,7 @@ module ietf-te-types { Generalized Multi-Protocol Label Switching (GMPLS) Recovery"; } + // CHANGE NOTE: The identity lsp-protection-reroute // below has been obsoleted in this module revision // RFC Editor: remove the note above and this note @@ -1746,7 +1732,6 @@ module ietf-te-types { description "Normal state."; } - identity signal-fail-of-protection { base lsp-protection-state; description @@ -1860,6 +1845,7 @@ module ietf-te-types { for Generalized Multi-Protocol Label Switching (GMPLS)"; } + identity clear-freeze { base protection-external-commands; description @@ -1986,7 +1972,6 @@ module ietf-te-types { "RFC 6004: Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 Ethernet Service Switching"; } - identity switching-l2sc { base switching-capabilities; description @@ -2004,6 +1989,7 @@ module ietf-te-types { "RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description"; } + identity switching-otn { base switching-capabilities; description @@ -2370,7 +2356,6 @@ module ietf-te-types { "RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP), section 7.8"; } - // CHANGE NOTE: The description and the reference of the // path-metric-hop identity have been updated // in this module revision @@ -2628,6 +2613,7 @@ module ietf-te-types { (PCEP) Extensions for the Hierarchical Path Computation Element (H-PCE) Architecture"; } + identity path-computation-error-pce-unavailable { base path-computation-error-reason; description @@ -2706,7 +2692,6 @@ module ietf-te-types { description "Path computation has failed because the destination domain was unknown. - It corresponds to bit 22 of the Flags field of the NO-PATH-VECTOR TLV."; reference @@ -2820,6 +2805,7 @@ module ietf-te-types { https://www.iana.org/assignments/pcep /pcep.xhtml#no-path-vector-tlv"; } + identity path-computation-error-destination-unknown { base path-computation-error-reason; description @@ -2916,6 +2902,7 @@ module ietf-te-types { Computation Element Communication Protocol (PCEP)"; } + identity svec-of-minimize-cost-path-set { base svec-objective-function-type; description @@ -3012,6 +2999,7 @@ module ietf-te-types { Computation Element Communication Protocol (PCEP)"; } + identity svec-metric-aggregate-bandwidth-consumption { base svec-metric-type; description @@ -3904,7 +3892,6 @@ module ietf-te-types { uses path-route-include-objects; } } - grouping common-constraints { description "Common constraints grouping that can be set on @@ -4444,17 +4431,25 @@ module ietf-te-types { } } - // CHANGE NOTE: The typedef te-gen-node-id below has been + // CHANGE NOTE: The grouping te-generic-node-id below has been // added in this module revision // RFC Editor: remove the note above and this note grouping te-generic-node-id { description "A reusable grouping for a TE generic node identifier."; leaf id { - type te-gen-node-id; + type union { + type te-node-id; + type inet:ip-address; + type nw:node-id; + } description - "The identifier of the node. Can be represented as IP - address or dotted quad address or as an URI."; + "The identifier of the node. + + It can be represented as IP address or dotted quad address + or as an URI. + + The type data node disambiguates the union type."; } leaf type { type enumeration { diff --git a/experimental/ietf-extracted-YANG-modules/ietf-template@2023-07-26.yang b/experimental/ietf-extracted-YANG-modules/ietf-template@2023-07-26.yang index 84f0f6501..3f00e31e8 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-template@2023-07-26.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-template@2023-07-26.yang @@ -8,14 +8,13 @@ module ietf-template { // replace this string, and try to pick a unique prefix prefix temp; - // import statements here: e.g., // import ietf-yang-types { prefix yang; } // import ietf-inet-types { prefix inet; } // identify the IETF working group if applicable organization - "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; + "IETF your-wg-name (Expanded WG Name) Working Group"; // update this contact statement with your info diff --git a/standard/iana/yang-parameters.xml b/standard/iana/yang-parameters.xml index fb2213cdc..3265f82f5 100644 --- a/standard/iana/yang-parameters.xml +++ b/standard/iana/yang-parameters.xml @@ -4,7 +4,7 @@ YANG Parameters 2010-06-10 - 2024-09-17 + 2024-09-27 YANG Module Names @@ -2019,15 +2019,15 @@ and Subsequent Address Family Identi - + ietf-syslog N urn:ietf:params:xml:ns:yang:ietf-syslog - ietf-syslog + syslog - - TEMPORARY - registered 2021-07-11, extension registered 2024-06-24, document sent to IESG Evaluation 2024-09-03. 's module file will be posted upon the document's publication as an RFC. + + 's module file will be posted upon the document's publication as an RFC. ietf-system