You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: draft-ietf-netmod-schedule-yang.md
+14-7Lines changed: 14 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -112,9 +112,15 @@ This document uses the YANG terminology defined in {{Section 3 of !RFC7950}}.
112
112
113
113
The document makes use of the following terms:
114
114
115
-
Recurrence Rule:
115
+
Recurrence rule:
116
116
: Refers to a rule or repeating pattern for recurring events. See also {{Section 3.8.5.3 of !RFC5545}} for a comprehensive iCalendar recurrence rule specification.
117
117
118
+
Recurrence instance (or Recurrence, for short):
119
+
: Refers to an instance that matches a recurrence rule.
120
+
121
+
Recurrence set:
122
+
: Refers to a set of recurrence instances.
123
+
118
124
Frequency:
119
125
: Characterizes the type of a recurrence rule. Values are taken from "FREQ" rule in {{Section 3.3.10 of !RFC5545}}.
120
126
: For example, repeating events based on an interval of a second or more are
@@ -125,7 +131,7 @@ iCalendar:
125
131
: Refers to Internet Calendaring per {{!RFC5545}}.
126
132
127
133
Interval:
128
-
: Refers to an integer that specifies at which interval a recurrence rule repeats. Values are taken from "INTERVAL" rule in {{Section 3.3.10 of !RFC5545}}.
134
+
: Refers to an integer that specifies interval at which a recurrence rule repeats. Values are taken from "INTERVAL" rule in {{Section 3.3.10 of !RFC5545}}.
129
135
: For example, "1", means every second for a secondly rule, every minute for a minutely rule, every hour for an hourly rule, etc.
130
136
131
137
System:
@@ -214,7 +220,7 @@ System:
214
220
The "discard-action" parameter specifies the action if a requested schedule
215
221
cannot be accepted for any reason and is discarded. Possible reasons include,
216
222
but are not limited to, the requested schedule failing to satisfy the guards in this grouping,
217
-
conflicting with existing schedules, or being out-of-date.
223
+
conflicting with existing schedules, or being out-of-date (e.g., the expected start is already passed).
218
224
219
225
These parameters apply to all schedules on a system and are meant
220
226
to provide guards against stale configuration, too short schedule requests
@@ -297,7 +303,7 @@ The interval specifies when a schedule will occur, combined with the frequency p
297
303
an occurrence will last. This document allows the interval between occurrences to be shorter than the duration of each occurrence (e.g., a recurring event is scheduled to start every day for a duration of 2 days).
298
304
299
305
The repetition can be scoped by a specified end time or by a count of occurrences,
300
-
indicated by the "recurrence-end" choice. The value of the "count" node MUST be greater than 1, the "start-time-utc" value always counts
306
+
indicated by the "recurrence-end" choice. The "count" value MUST be greater than 1, the "start-time-utc" value always counts
301
307
as the first occurrence.
302
308
303
309
The "recurrence-utc" grouping is designed to be reused in scheduling contexts
@@ -327,7 +333,7 @@ an occurrence will last. This document allows the interval between occurrences t
327
333
values which are specified in the format of UTC or time zone offset to UTC.
328
334
329
335
The repetition can be scoped by a specified end time or by a count of occurrences,
330
-
indicated by the "recurrence-end" choice. The value of the "count" node MUST be greater than 1, the "start-time" value always counts
336
+
indicated by the "recurrence-end" choice. The "count" value MUST be greater than 1, the "start-time" value always counts
331
337
as the first occurrence.
332
338
333
339
Unlike the definition of "recurrence-utc" grouping ({{sec-rec-utc}}),
@@ -1015,6 +1021,7 @@ after that time would not be considered as valid.
1015
1021
Other related efforts were explored in the past, e.g., {{?I-D.liu-netmod-yang-schedule}}.
1016
1022
1017
1023
Thanks to Reshad Rahman for the great YANG Doctors review, Mahesh Jethanandani for the AD review, Per Andersson for the OPSDIR review,
1018
-
and Peter Yee for genart review.
1024
+
Peter Yee for genart review, and Acee Lindem for the rtgdir review.
1025
+
1026
+
Thanks to Éric Vyncke and Erik Kline for the IESG review.
0 commit comments