rfc9922v1.txt		rfc9922.txt
	skipping to change at line 174 ¶		skipping to change at line 174 ¶
	Interval: Refers to an integer that specifies the interval at which		Interval: Refers to an integer that specifies the interval at which
	a recurrence rule repeats. Values are taken from the "INTERVAL"		a recurrence rule repeats. Values are taken from the "INTERVAL"
	rule in Section 3.3.10 of [RFC5545].		rule in Section 3.3.10 of [RFC5545].
	For example, "1" means every second for a secondly rule, every		For example, "1" means every second for a secondly rule, every
	minute for a minutely rule, every hour for an hourly rule, etc.		minute for a minutely rule, every hour for an hourly rule, etc.
	System: Refers to an entity that hosts a schedule that is managed		System: Refers to an entity that hosts a schedule that is managed
	using the YANG module defined in this document.		using the YANG module defined in this document.
			"schedule-status-*" refers to any of "schedule-status", "schedule-
			status-with-time-zone", and "schedule-status-with-name".
	3. Module Overview		3. Module Overview
	3.1. Features		3.1. Features
	The "ietf-schedule" data model defines the recurrence-related		The "ietf-schedule" data model defines the recurrence-related
	groupings using a modular approach. To that aim, a variety of		groupings using a modular approach. To that aim, a variety of
	representations of recurrence groupings ranging from basic to		representations of recurrence groupings ranging from basic to
	advanced (iCalender-like) are defined. To allow for different		advanced (iCalender-like) are defined. To allow for different
	options, two features are defined in the data model:		options, two features are defined in the data model:
	skipping to change at line 198 ¶		skipping to change at line 201 ¶
	Refer to Section 3.4 and Appendix B.1 for the use of these features.		Refer to Section 3.4 and Appendix B.1 for the use of these features.
	3.2. Types and Identities		3.2. Types and Identities
	The "ietf-schedule" module (Section 6) defines the following		The "ietf-schedule" module (Section 6) defines the following
	identities:		identities:
	* "schedule-type": Indicates the type of schedule. The following		* "schedule-type": Indicates the type of schedule. The following
	types are defined so far:		types are defined so far:
	- one-shot: The schedule will trigger an action that has either		- one-shot: This type is used for a schedule that triggers an
	the duration specified as 0 or the end time specified as the		action that has either the duration specified as 0 or the end
	same as the start time, and then the schedule will disable		time specified as the same as the start time, and then the
	itself (Section 3.3 of [RFC3231]).		schedule will disable itself (Section 3.3 of [RFC3231]).
	- period: This type is used for a period-based schedule		- period: This type is used for a period-based schedule
	consisting of either (1) a start and end or (2) a start and		consisting of either (1) a start and end or (2) a start and
	positive duration of time. If neither an end nor a duration is		positive duration of time. If neither an end nor a duration is
	indicated, the period is considered to last forever.		indicated, the period is considered to last forever.
	- recurrence: This type is used for a recurrence-based schedule.		- recurrence: This type is used for a recurrence-based schedule.
	A recurrence may be periodic (i.e., repeat over the same		A recurrence may be periodic (i.e., repeat over the same
	period, e.g., every five minutes) or not (i.e., repeat in a		period, e.g., every five minutes) or not (i.e., repeat in a
	non-regular manner, e.g., every day at 8 and 9 AM).		non-regular manner, e.g., every day at 8 and 9 AM).
	skipping to change at line 285 ¶		skipping to change at line 288 ¶
	The "time-zone-identifier" parameter, if provided, specifies the time		The "time-zone-identifier" parameter, if provided, specifies the time
	zone reference [RFC7317] of the local date and time values. This		zone reference [RFC7317] of the local date and time values. This
	parameter MUST be specified if any of the date and time values are in		parameter MUST be specified if any of the date and time values are in
	the format of local time. It MUST NOT be applied to date and time		the format of local time. It MUST NOT be applied to date and time
	values that are specified in the format of UTC or time zone offset to		values that are specified in the format of UTC or time zone offset to
	UTC.		UTC.
	The "validity" parameter specifies the date and time after which a		The "validity" parameter specifies the date and time after which a
	schedule will not be considered as valid. It determines the latest		schedule will not be considered as valid. It determines the latest
	time that a schedule can be started to execute independent of when it		time that a schedule can be started and thus executed independently
	ends, and it takes precedence over similar attributes that are		from when it ends, and it takes precedence over similar attributes
	provided at the schedule instance itself. A requested schedule may		that are provided at the schedule instance itself. A requested
	still be accepted, but any occurrences that start later than the		schedule may still be accepted, but any occurrences that start later
	configured value will not be executed.		than the configured value will not be executed.
	The "max/min-allowed-start" parameters specify the maximum/minimum		The "max/min-allowed-start" parameters specify the maximum/minimum
	scheduled start date and time. A requested schedule will be rejected		scheduled start date and time. A requested schedule will be rejected
	if the first occurrence of the schedule starts later/earlier than the		if the first occurrence of the schedule starts later/earlier than the
	configured values.		configured values.
	The "max-allowed-end" parameter specifies the maximum allowed end		The "max-allowed-end" parameter specifies the maximum allowed end
	time of the last occurrence. A requested schedule will be rejected		time of the last occurrence. A requested schedule will be rejected
	if the end time of the last occurrence is later than the configured		if the end time of the last occurrence is later than the configured
	"max-allowed-end" value.		"max-allowed-end" value.
	The "discard-action" parameter specifies the action if a requested		The "discard-action" parameter specifies the action if a requested
	schedule cannot be accepted for any reason and is discarded.		schedule cannot be accepted for any reason and is discarded.
	Possible reasons include, but are not limited to, the requested		Possible reasons include, but are not limited to, the requested
	schedule failing to satisfy the guards in this grouping, conflicting		schedule failing to satisfy the guards in this grouping, conflicting
	with existing schedules, or being out-of-date (e.g., the expected		with existing schedules, or being out-of-date (e.g., the expected
	start has already passed).		start has already passed).
	*
	These parameters apply to all schedules on a system and are meant to		These parameters apply to all schedules on a system and are meant to
	provide guards against stale configuration, too short schedule		provide guards against stale configuration, schedule requests that
	requests that would prevent validation by admins of some critical		are too short and that would thus prevent validation by admins of
	systems, etc.		some critical systems, etc.
	3.3.2. The "period-of-time" Grouping		3.3.2. The "period-of-time" Grouping
	The "period-of-time" grouping (Figure 2) represents a time period		The "period-of-time" grouping (Figure 2) represents a time period
	using either a start date and time ("period-start") and end date and		using either a start date and time ("period-start") and end date and
	time ("period-end") or a start date and time ("period-start") and a		time ("period-end") or a start date and time ("period-start") and a
	non-negative time duration ("duration"). For the first format, the		non-negative time duration ("duration"). For the first format, the
	start of the period MUST be no later than the end of the period. If		start of the period MUST be no later than the end of the period. If
	neither an end date and time ("period-end") nor a duration		neither an end date and time ("period-end") nor a duration
	("duration") is indicated, the period is considered to last forever.		("duration") is indicated, the period is considered to last forever.
	skipping to change at line 373 ¶		skipping to change at line 374 ¶
	The frequency parameter ("frequency") identifies the type of		The frequency parameter ("frequency") identifies the type of
	recurrence rule. For example, a "daily" frequency value specifies		recurrence rule. For example, a "daily" frequency value specifies
	repeating events based on an interval of a day or more.		repeating events based on an interval of a day or more.
	Consistent with Section 3.3.10 of [RFC5545], the interval parameter		Consistent with Section 3.3.10 of [RFC5545], the interval parameter
	("interval") represents at which interval the recurrence rule		("interval") represents at which interval the recurrence rule
	repeats. For example, within a "daily" recurrence rule, an interval		repeats. For example, within a "daily" recurrence rule, an interval
	value of "8" means every eight days.		value of "8" means every eight days.
	Note that, per Section 4.13 of [YANG-GUIDE], neither a "default" nor		Note that, per Section 4.13 of [YANG-GUIDE], no "default"
	a "mandatory" substatement is defined here for both "frequency" and		substatement is defined here for both "frequency" and "interval"
	"interval" parameters because there are cases (e.g., profiling) where		parameters because there are cases (e.g., profiling) where using
	using these statements is problematic. YANG modules using this		these statements is problematic. No "mandatory" substatement is
	grouping SHOULD refine these two nodes with either a "mandatory" or a		defined here for the same reason. YANG modules using this grouping
			SHOULD refine these two nodes with either a "mandatory" or a
	"default" statement if they always need to be configured or have		"default" statement if they always need to be configured or have
	default values. This recommendation MAY be ignored in cases such as		default values. This recommendation MAY be ignored in cases such as
	when this grouping is used by another grouping.		when this grouping is used by another grouping.
	The "recurrence-description" parameter includes a description of the		The "recurrence-description" parameter includes a description of the
	period. No constraint is imposed on the structure nor the use of		period. No constraint is imposed on the structure nor the use of
	this parameter.		this parameter.
	3.3.4. The "recurrence-utc" Grouping		3.3.4. The "recurrence-utc" Grouping
	skipping to change at line 514 ¶		skipping to change at line 516 ¶
	+-- frequency? identityref		+-- frequency? identityref
	+-- interval? uint32		+-- interval? uint32
	+-- period-timeticks* [period-start]		+-- period-timeticks* [period-start]
	+-- period-start yang:timeticks		+-- period-start yang:timeticks
	+-- period-end? yang:timeticks		+-- period-end? yang:timeticks
	Figure 6: 'recurrence-utc-with-periods' Grouping Tree Structure		Figure 6: 'recurrence-utc-with-periods' Grouping Tree Structure
	The recurrence instances are specified by the union of occurrences		The recurrence instances are specified by the union of occurrences
	defined by both the recurrence rule and "period-timeticks" list.		defined by both the recurrence rule and "period-timeticks" list.
	This list uses the "yang:timeticks" type defined in [RFC6991].		This list uses the "yang:timeticks" type defined in [RFC9911].
	Duplicate instances are ignored. The value of the "period-start"		Duplicate instances are ignored. The value of the "period-start"
	instance MUST NOT exceed the value indicated by the value of the		instance MUST NOT exceed the value of the "frequency" instance, i.e.,
	"frequency" instance, i.e., the "timeticks" value must not exceed 100		the "timeticks" value must not exceed 100 in a secondly recurrence
	in a secondly recurrence rule, and it must not exceed 6000 in a		rule, and it must not exceed 6000 in a minutely recurrence rule, and
	minutely recurrence rule, and so on.		so on.
	3.3.7. The "recurrence-time-zone-with-periods" Grouping		3.3.7. The "recurrence-time-zone-with-periods" Grouping
	The "recurrence-time-zone-with-periods" grouping (Figure 7) uses the		The "recurrence-time-zone-with-periods" grouping (Figure 7) uses the
	"recurrence-with-time-zone" grouping (Section 3.3.5) and adds a		"recurrence-with-time-zone" grouping (Section 3.3.5) and adds a
	"period" list to define an aggregate set of repeating occurrences.		"period" list to define an aggregate set of repeating occurrences.
	grouping recurrence-time-zone-with-periods:		grouping recurrence-time-zone-with-periods:
	+-- recurrence-first		+-- recurrence-first
	| +-- start-time? yang:date-and-time		| +-- start-time? yang:date-and-time
	skipping to change at line 638 ¶		skipping to change at line 640 ¶
	occurrence within the set of recurrence instances to be specified.		occurrence within the set of recurrence instances to be specified.
	For example, in a "monthly" recurrence rule, the "byday" data node		For example, in a "monthly" recurrence rule, the "byday" data node
	specifies every Monday of the week, and the "bysetpos" with a value		specifies every Monday of the week, and the "bysetpos" with a value
	of "-1" represents the last Monday of the month. Not setting the		of "-1" represents the last Monday of the month. Not setting the
	"bysetpos" data node represents every Monday of the month.		"bysetpos" data node represents every Monday of the month.
	The "workweek-start" data node specifies the day on which the week		The "workweek-start" data node specifies the day on which the week
	starts. This is significant when a "weekly" recurrence rule has an		starts. This is significant when a "weekly" recurrence rule has an
	interval greater than 1, and a "byday" data node is specified. This		interval greater than 1, and a "byday" data node is specified. This
	is also significant when in a "yearly" rule and a "byyearweek" is		is also significant when in a "yearly" rule and a "byyearweek" is
	specified. Note that, per Section 4.13 of [YANG-GUIDE], neither a		specified. Note that, per Section 4.13 of [YANG-GUIDE], no "default"
	"default" nor a "mandatory" substatement is defined here because		substatement is defined here because there are cases (e.g.,
	there are cases (e.g., profiling) where using these statements is		profiling) where using these statements is problematic. No
	problematic. YANG modules using this grouping SHOULD refine the		"mandatory" substatement is defined here for the same reason. YANG
	"workweek-start" node with either a "mandatory" or a "default"		modules using this grouping SHOULD refine the "workweek-start" node
	statement if it always needs to be configured or has a default value.		with either a "mandatory" or a "default" statement if it always needs
	This MAY be ignored in cases such as when this grouping is used by		to be configured or has a default value. This MAY be ignored in
	another grouping.		cases such as when this grouping is used by another grouping.
	The "exception-dates" data node specifies a list of exceptions for		The "exception-dates" data node specifies a list of exceptions for
	recurrence. The final recurrence set is generated by gathering all		recurrence. The final recurrence set is generated by gathering all
	of the date and time values created by any of the specified		of the date and time values created by any of the specified
	recurrence rules and date-times and then excluding any start date and		recurrence rules and date-times and then excluding any start date and
	time values specified by "exception-dates" parameter.		time values specified by "exception-dates" parameter.
	3.3.9. The "schedule-status", "schedule-status-with-time-zone", and		3.3.9. The "schedule-status", "schedule-status-with-time-zone", and
	"schedule-status-with-name" Groupings		"schedule-status-with-name" Groupings
	skipping to change at line 845 ¶		skipping to change at line 847 ¶
	+------------------+-------------------------+		+------------------+-------------------------+
	| schedValue | Not applicable |		| schedValue | Not applicable |
	+------------------+-------------------------+		+------------------+-------------------------+
	| schedTriggers | counter/failure-counter |		| schedTriggers | counter/failure-counter |
	+------------------+-------------------------+		+------------------+-------------------------+
	Table 1: YANG/MIB Mapping		Table 1: YANG/MIB Mapping
	6. The "ietf-schedule" YANG Module		6. The "ietf-schedule" YANG Module
	This module imports types defined in [RFC5545], [RFC6991], and		This module imports types defined in [RFC9911] and [RFC7317].
	[RFC7317].
	<CODE BEGINS>		<CODE BEGINS>
	file "ietf-schedule@2026-02-18.yang"		file "ietf-schedule@2026-02-18.yang"
	module ietf-schedule {		module ietf-schedule {
	yang-version 1.1;		yang-version 1.1;
	namespace "urn:ietf:params:xml:ns:yang:ietf-schedule";		namespace "urn:ietf:params:xml:ns:yang:ietf-schedule";
	prefix schedule;		prefix schedule;
	import ietf-yang-types {		import ietf-yang-types {
	prefix yang;		prefix yang;
	reference		reference
	"RFC 6991: Common YANG Data Types";		"RFC 9911: Common YANG Data Types";
	}		}
	import ietf-system {		import ietf-system {
	prefix sys;		prefix sys;
	reference		reference
	"RFC 7317: A YANG Data Model for System Management";		"RFC 7317: A YANG Data Model for System Management";
	}		}
	organization		organization
	"IETF NETMOD Working Group";		"IETF NETMOD Working Group";
	skipping to change at line 1744 ¶		skipping to change at line 1745 ¶
	RESTCONF protocol operations and content.		RESTCONF protocol operations and content.
	The "ietf-schedule" module defines a set of identities, types, and		The "ietf-schedule" module defines a set of identities, types, and
	groupings. These nodes are intended to be reused by other YANG		groupings. These nodes are intended to be reused by other YANG
	modules. The module by itself does not expose any data nodes that		modules. The module by itself does not expose any data nodes that
	are writable, data nodes that contain read-only state, or RPCs. As		are writable, data nodes that contain read-only state, or RPCs. As
	such, there are no additional security issues related to the "ietf-		such, there are no additional security issues related to the "ietf-
	schedule" module that need to be considered.		schedule" module that need to be considered.
	Modules that use the groupings that are defined in this document		Modules that use the groupings that are defined in this document
	should identify the corresponding security considerations, for		should identify the corresponding security considerations. For
	example:		example, reuising the following groupings will expose privacy-related
			information:
	* Scheduling depends on reliable and accurate time synchronization.		* Scheduling depends on reliable and accurate time synchronization.
	Inaccurate date and time setting can lead to scheduling events		Inaccurate date and time setting can lead to scheduling events
	being triggered at incorrect intervals, potentially causing system		being triggered at incorrect intervals, potentially causing system
	failures or security vulnerabilities.		failures or security vulnerabilities.
	* Recurring events may conceal abnormal behavior or security		* Recurring events may conceal abnormal behavior or security
	threats, which may be drowned out by normal events, especially		threats, which may be drowned out by normal events, especially
	when they are triggered frequently.		when they are triggered frequently.
	skipping to change at line 1821 ¶		skipping to change at line 1823 ¶
	[RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and		[RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and
	Scheduling Core Object Specification (iCalendar)",		Scheduling Core Object Specification (iCalendar)",
	RFC 5545, DOI 10.17487/RFC5545, September 2009,		RFC 5545, DOI 10.17487/RFC5545, September 2009,
	<https://www.rfc-editor.org/info/rfc5545>.		<https://www.rfc-editor.org/info/rfc5545>.
	[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for		[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
	the Network Configuration Protocol (NETCONF)", RFC 6020,		the Network Configuration Protocol (NETCONF)", RFC 6020,
	DOI 10.17487/RFC6020, October 2010,		DOI 10.17487/RFC6020, October 2010,
	<https://www.rfc-editor.org/info/rfc6020>.		<https://www.rfc-editor.org/info/rfc6020>.
	[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
	RFC 6991, DOI 10.17487/RFC6991, July 2013,
	<https://www.rfc-editor.org/info/rfc6991>.
	[RFC7317] Bierman, A. and M. Bjorklund, "A YANG Data Model for		[RFC7317] Bierman, A. and M. Bjorklund, "A YANG Data Model for
	System Management", RFC 7317, DOI 10.17487/RFC7317, August		System Management", RFC 7317, DOI 10.17487/RFC7317, August
	2014, <https://www.rfc-editor.org/info/rfc7317>.		2014, <https://www.rfc-editor.org/info/rfc7317>.
	[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",		[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
	RFC 7950, DOI 10.17487/RFC7950, August 2016,		RFC 7950, DOI 10.17487/RFC7950, August 2016,
	<https://www.rfc-editor.org/info/rfc7950>.		<https://www.rfc-editor.org/info/rfc7950>.
	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC		[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,		2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration		[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
	Access Control Model", STD 91, RFC 8341,		Access Control Model", STD 91, RFC 8341,
	DOI 10.17487/RFC8341, March 2018,		DOI 10.17487/RFC8341, March 2018,
	<https://www.rfc-editor.org/info/rfc8341>.		<https://www.rfc-editor.org/info/rfc8341>.
	[W3C.XML1.0]		[RFC9911] Schönwälder, J., Ed., "Common YANG Data Types", RFC 9911,
	Bray, T., Ed., Paoli, J., Ed., Sperberg-McQueen, C. M.,		DOI 10.17487/RFC9911, December 2025,
	Ed., Maler, E., Ed., and F. Yergeau, Ed., "Extensible		<https://www.rfc-editor.org/info/rfc9911>.
	Markup Language (XML) 1.0 (Fifth Edition)", W3C
	Recommendation, 26 November 2008,
	<https://www.w3.org/TR/2008/REC-xml-20081126/>.
	9.2. Informative References		9.2. Informative References
	[NETMOD-ECA-POLICY]		[NETMOD-ECA-POLICY]
	Wu, Q., Bryskin, I., Birkholz, H., Liu, X., and B. Claise,		Wu, Q., Bryskin, I., Birkholz, H., Liu, X., and B. Claise,
	"A YANG Data model for ECA Policy Management", Work in		"A YANG Data model for ECA Policy Management", Work in
	Progress, Internet-Draft, draft-ietf-netmod-eca-policy-01,		Progress, Internet-Draft, draft-ietf-netmod-eca-policy-01,
	19 February 2021, <https://datatracker.ietf.org/doc/html/		19 February 2021, <https://datatracker.ietf.org/doc/html/
	draft-ietf-netmod-eca-policy-01>.		draft-ietf-netmod-eca-policy-01>.
	skipping to change at line 1889 ¶		skipping to change at line 1884 ¶
	<https://www.rfc-editor.org/info/rfc7951>.		<https://www.rfc-editor.org/info/rfc7951>.
	[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF		[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
	Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,		Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
	<https://www.rfc-editor.org/info/rfc8040>.		<https://www.rfc-editor.org/info/rfc8040>.
	[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",		[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
	BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,		BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
	<https://www.rfc-editor.org/info/rfc8340>.		<https://www.rfc-editor.org/info/rfc8340>.
			[RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N.,
			Ananthakrishnan, H., and X. Liu, "A YANG Data Model for
			Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March
			2018, <https://www.rfc-editor.org/info/rfc8345>.
	[RFC8413] Zhuang, Y., Wu, Q., Chen, H., and A. Farrel, "Framework		[RFC8413] Zhuang, Y., Wu, Q., Chen, H., and A. Farrel, "Framework
	for Scheduled Use of Resources", RFC 8413,		for Scheduled Use of Resources", RFC 8413,
	DOI 10.17487/RFC8413, July 2018,		DOI 10.17487/RFC8413, July 2018,
	<https://www.rfc-editor.org/info/rfc8413>.		<https://www.rfc-editor.org/info/rfc8413>.
	[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol		[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
	Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,		Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
	<https://www.rfc-editor.org/info/rfc8446>.		<https://www.rfc-editor.org/info/rfc8446>.
	[RFC9000] Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based		[RFC9000] Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based
	Multiplexed and Secure Transport", RFC 9000,		Multiplexed and Secure Transport", RFC 9000,
	DOI 10.17487/RFC9000, May 2021,		DOI 10.17487/RFC9000, May 2021,
	<https://www.rfc-editor.org/info/rfc9000>.		<https://www.rfc-editor.org/info/rfc9000>.
	[RFC9657] Birrane, III, E., Kuhn, N., Qu, Y., Taylor, R., and L.		[RFC9657] Birrane, III, E., Kuhn, N., Qu, Y., Taylor, R., and L.
	Zhang, "Time-Variant Routing (TVR) Use Cases", RFC 9657,		Zhang, "Time-Variant Routing (TVR) Use Cases", RFC 9657,
	DOI 10.17487/RFC9657, October 2024,		DOI 10.17487/RFC9657, October 2024,
	<https://www.rfc-editor.org/info/rfc9657>.		<https://www.rfc-editor.org/info/rfc9657>.
			[W3C.XML1.0]
			Bray, T., Ed., Paoli, J., Ed., Sperberg-McQueen, C. M.,
			Ed., Maler, E., Ed., and F. Yergeau, Ed., "Extensible
			Markup Language (XML) 1.0 (Fifth Edition)", W3C
			Recommendation, 26 November 2008,
			<https://www.w3.org/TR/2008/REC-xml-20081126/>.
	[YANG-CONFIG-SCHEDULE]		[YANG-CONFIG-SCHEDULE]
	Liu, X., Bryskin, I., Beeram, V. P., Saad, T., Shah, H.		Liu, X., Bryskin, I., Beeram, V. P., Saad, T., Shah, H.
	C., and O. G. de Dios, "A YANG Data Model for		C., and O. G. de Dios, "A YANG Data Model for
	Configuration Scheduling", Work in Progress, Internet-		Configuration Scheduling", Work in Progress, Internet-
	Draft, draft-liu-netmod-yang-schedule-05, 1 March 2018,		Draft, draft-liu-netmod-yang-schedule-05, 1 March 2018,
	<https://datatracker.ietf.org/doc/html/draft-liu-netmod-		<https://datatracker.ietf.org/doc/html/draft-liu-netmod-
	yang-schedule-05>.		yang-schedule-05>.
	[YANG-GUIDE]		[YANG-GUIDE]
	Bierman, A., Boucadair, M., and Q. Wu, "Guidelines for		Bierman, A., Boucadair, M., and Q. Wu, "Guidelines for
	skipping to change at line 2433 ¶		skipping to change at line 2440 ¶
	organization		organization
	"Example, Inc.";		"Example, Inc.";
	contact		contact
	"Support at example.com";		"Support at example.com";
	description		description
	"Example of a module defining a scheduled-based backup		"Example of a module defining a scheduled-based backup
	operation.";		operation.";
	revision "2023-01-19" {		revision "2026-02-20" {
	description		description
	"Initial version.";		"Initial version.";
	reference		reference
	"RFC 9922: A YANG Data Model for Scheduling.";		"RFC 9922: A YANG Data Model for Scheduling.";
	}		}
	container scheduled-backup-tasks {		container scheduled-backup-tasks {
	description		description
	"A container for backing up all current running configurations		"A container for backing up all current running configurations
	on the device.";		on the device.";
	skipping to change at line 2538 ¶		skipping to change at line 2545 ¶
	}		}
	}		}
	B.2. Example: Schedule Network Properties to Change Based on Date and		B.2. Example: Schedule Network Properties to Change Based on Date and
	Time		Time
	Network properties may change over a specific period of time or based		Network properties may change over a specific period of time or based
	on a recurrence rule, e.g., [RFC9657]. The following example module,		on a recurrence rule, e.g., [RFC9657]. The following example module,
	which augments the "recurrence-utc-with-periods" grouping from the		which augments the "recurrence-utc-with-periods" grouping from the
	"ietf-schedule" module, shows how a scheduled attribute could be		"ietf-schedule" module, shows how a scheduled attribute could be
	defined.		defined. Note that
			[RFC8345] and this document are referenced in the module.
	module example-scheduled-link-bandwidth {		module example-scheduled-link-bandwidth {
	yang-version 1.1;		yang-version 1.1;
	namespace "http://example.com/example-scheduled-link-bandwidth";		namespace "http://example.com/example-scheduled-link-bandwidth";
	prefix "ex-scattr";		prefix "ex-scattr";
	import ietf-network {		import ietf-network {
	prefix "nw";		prefix "nw";
	reference		reference
	"RFC 8345: A YANG Data Model for Network Topologies";		"RFC 8345: A YANG Data Model for Network Topologies";
	skipping to change at line 2566 ¶		skipping to change at line 2574 ¶
	organization		organization
	"Example, Inc.";		"Example, Inc.";
	contact		contact
	"Support at example.com";		"Support at example.com";
	description		description
	"Example of a module defining a scheduled link bandwidth.";		"Example of a module defining a scheduled link bandwidth.";
	revision "2023-01-19" {		revision "2026-02-20" {
	description		description
	"Initial version.";		"Initial version.";
	reference		reference
	"RFC 9922: A YANG Data Model for Scheduling";		"RFC 9922: A YANG Data Model for Scheduling";
	}		}
	grouping link-bandwidth-grouping {		grouping link-bandwidth-grouping {
	description		description
	"Grouping of the link bandwidth definition.";		"Grouping of the link bandwidth definition.";
	leaf scheduled-bandwidth {		leaf scheduled-bandwidth {
End of changes. 19 change blocks.
	50 lines changed or deleted		58 lines changed or added
This html diff was produced by rfcdiff 1.48.