rfc9922v2.txt   rfc9922.txt 
skipping to change at line 1746 skipping to change at line 1746
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, reuising the following groupings will expose privacy-related example, reusing the following groupings will expose privacy-related
information: 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 1969 skipping to change at line 1969
module example-sch-usage-1 { module example-sch-usage-1 {
yang-version 1.1; yang-version 1.1;
namespace "http://example.com/example-sch-usage-1"; namespace "http://example.com/example-sch-usage-1";
prefix "ex-schu-1"; prefix "ex-schu-1";
import ietf-schedule { import ietf-schedule {
prefix "schedule"; prefix "schedule";
} }
organization
"Example, Inc.";
contact
"Support at example.com";
description
"Example of a module using 'generic-schedule-params' and
'schedule-status' groupings.";
revision "2026-02-20" {
description "Initial version.";
reference
"RFC 9922: A YANG Data Model for Scheduling.";
}
container generic-schedule-params { container generic-schedule-params {
description
"A collection of generic scheduling parameters.";
uses schedule:generic-schedule-params; uses schedule:generic-schedule-params;
} }
container schedule-status { container schedule-status {
description
"A collection of scheduling status.";
uses schedule:schedule-status; uses schedule:schedule-status;
} }
} }
module example-sch-usage-2 { module example-sch-usage-2 {
yang-version 1.1; yang-version 1.1;
namespace "http://example.com/example-sch-usage-2"; namespace "http://example.com/example-sch-usage-2";
prefix "ex-schu2"; prefix "ex-schu2";
import ietf-schedule { import ietf-schedule {
prefix "schedule"; prefix "schedule";
} }
organization
"Example, Inc.";
contact
"Support at example.com";
description
"Example of a module using the 'period-of-time' grouping.";
revision "2026-02-20" {
description "Initial version.";
reference
"RFC 9922: A YANG Data Model for Scheduling.";
}
container period-of-time { container period-of-time {
description
"A container for a time period.";
uses schedule:period-of-time; uses schedule:period-of-time;
} }
} }
module example-sch-usage-3 { module example-sch-usage-3 {
yang-version 1.1; yang-version 1.1;
namespace "http://example.com/example-sch-usage-3"; namespace "http://example.com/example-sch-usage-3";
prefix "ex-schu-3"; prefix "ex-schu-3";
import ietf-schedule { import ietf-schedule {
prefix "schedule"; prefix "schedule";
} }
organization
"Example, Inc.";
contact
"Support at example.com";
description
"Example of a module using the 'recurrence-basic' grouping.";
revision "2026-02-20" {
description "Initial version.";
reference
"RFC 9922: A YANG Data Model for Scheduling.";
}
container recurrence-basic { container recurrence-basic {
description
"A container for a simple recurrence rule.";
uses schedule:recurrence-basic { uses schedule:recurrence-basic {
refine frequency {
mandatory true;
}
refine interval { refine interval {
default 1; default 1;
} }
} }
} }
} }
module example-sch-usage-4 { module example-sch-usage-4 {
yang-version 1.1; yang-version 1.1;
namespace "http://example.com/example-sch-usage-4"; namespace "http://example.com/example-sch-usage-4";
prefix "ex-schu-4"; prefix "ex-schu-4";
import ietf-schedule { import ietf-schedule {
prefix "schedule"; prefix "schedule";
} }
organization
"Example, Inc.";
contact
"Support at example.com";
description
"Example of a module using the 'recurrence-utc' grouping.";
revision "2026-02-20" {
description "Initial version.";
reference
"RFC 9922: A YANG Data Model for Scheduling.";
}
container recurrence-utc { container recurrence-utc {
description
"A container for a simple recurrence rule in UTC format.";
uses schedule:recurrence-utc; uses schedule:recurrence-utc;
} }
} }
module example-sch-usage-5 { module example-sch-usage-5 {
yang-version 1.1; yang-version 1.1;
namespace "http://example.com/example-sch-usage-5"; namespace "http://example.com/example-sch-usage-5";
prefix "ex-schu-5"; prefix "ex-schu-5";
import ietf-schedule { import ietf-schedule {
prefix "schedule"; prefix "schedule";
} }
organization
"Example, Inc.";
contact
"Support at example.com";
description
"Example of a module using the 'recurrence-with-time-zone'
grouping.";
revision "2026-02-20" {
description "Initial version.";
reference
"RFC 9922: A YANG Data Model for Scheduling.";
}
container recurrence-with-time-zone { container recurrence-with-time-zone {
description
"A container for a simple recurrence rule with a time zone.";
uses schedule:recurrence-with-time-zone; uses schedule:recurrence-with-time-zone;
} }
} }
module example-sch-usage-6 { module example-sch-usage-6 {
yang-version 1.1; yang-version 1.1;
namespace "http://example.com/example-sch-usage-6"; namespace "http://example.com/example-sch-usage-6";
prefix "ex-schu-6"; prefix "ex-schu-6";
import ietf-schedule { import ietf-schedule {
prefix "schedule"; prefix "schedule";
} }
container recurrence-utc-with-date-times { organization
"Example, Inc.";
contact
"Support at example.com";
description
"Example of a module using the 'recurrence-utc-with-periods'
grouping.";
revision "2026-02-20" {
description "Initial version.";
reference
"RFC 9922: A YANG Data Model for Scheduling.";
}
container recurrence-utc-with-periods {
description
"A container for an aggregate set of repeating occurrences in
UTC format.";
uses schedule:recurrence-utc-with-periods; uses schedule:recurrence-utc-with-periods;
} }
} }
module example-sch-usage-7 { module example-sch-usage-7 {
yang-version 1.1; yang-version 1.1;
namespace "http://example.com/example-sch-usage-7"; namespace "http://example.com/example-sch-usage-7";
prefix "ex-schu-8"; prefix "ex-schu-8";
import ietf-schedule { import ietf-schedule {
prefix "schedule"; prefix "schedule";
}
container recurrence-time-zone-with-date-times { organization
"Example, Inc.";
contact
"Support at example.com";
description
"Example of a module using the
'recurrence-time-zone-with-periods' grouping.";
revision "2026-02-20" {
description "Initial version.";
reference
"RFC 9922: A YANG Data Model for Scheduling.";
}
container recurrence-time-zone-with-periods {
description
"A container for an aggregate set of repeating occurrences
with a time zone.";
uses schedule:recurrence-time-zone-with-periods; uses schedule:recurrence-time-zone-with-periods;
} }
} }
module example-sch-usage-8 { module example-sch-usage-8 {
yang-version 1.1; yang-version 1.1;
namespace "http://example.com/example-sch-usage-8"; namespace "http://example.com/example-sch-usage-8";
prefix "ex-schu-8"; prefix "ex-schu-8";
import ietf-schedule {
prefix "schedule";
}
organization
"Example, Inc.";
contact
"Support at example.com";
description
"Example of a module using 'icalendar-recurrence' grouping.";
revision "2026-02-20" {
description "Initial version.";
reference
"RFC 9922: A YANG Data Model for Scheduling.";
}
container icalendar-recurrence { container icalendar-recurrence {
description
"A container for a scheduled iCalendar recurrence.";
uses schedule:icalendar-recurrence { uses schedule:icalendar-recurrence {
refine workweek-start { refine workweek-start {
default monday; default monday;
} }
} }
} }
} }
For each example, only the message body is provided with JSON, which For each example, only the message body is provided with JSON, which
is used for encoding per the guidance in [RFC7951]. is used for encoding per the guidance in [RFC7951].
skipping to change at line 2698 skipping to change at line 2844
prefix "ex-schecaparev"; prefix "ex-schecaparev";
import ietf-network-topology { import ietf-network-topology {
prefix "nt"; prefix "nt";
} }
import ietf-schedule { import ietf-schedule {
prefix "schedule"; prefix "schedule";
} }
organization
"Example, Inc.";
contact
"Support at example.com";
description
"An example to show a scheduled link capacity reservation.";
revision "2026-02-20" {
description
"Initial version.";
reference
"RFC 9922: A YANG Data Model for Scheduling";
}
container link-capability-reservations { container link-capability-reservations {
description
"A container for a scheduled link capability reservations";
list scheduled-link-capacity { list scheduled-link-capacity {
key "schedule-id"; key "schedule-id";
description
"Definition of scheduled link capacity list";
leaf schedule-id { leaf schedule-id {
type string; type string;
description
"The schedule identifier for this schedule rule.";
} }
leaf link-id { leaf link-id {
type nt:link-id; type nt:link-id;
description
"The identifier of a link in the topology.";
} }
leaf reserved-capability { leaf reserved-capability {
type uint64; type uint64;
units "Mbps"; units "Mbps";
description
"The reserved capability for a particular link.";
} }
uses schedule:period-of-time; uses schedule:period-of-time;
} }
} }
} }
Section 4 of [RFC8413] defines the reference architecture for Section 4 of [RFC8413] defines the reference architecture for
scheduled use of resources. The service requester sends a request to scheduled use of resources. The service requester sends a request to
a Path Computation Element (PCE) and includes the parameters of the a Path Computation Element (PCE) and includes the parameters of the
Label Switched Path (LSP) that the requester wishes to supply. The Label Switched Path (LSP) that the requester wishes to supply. The
 End of changes. 24 change blocks. 
6 lines changed or deleted 178 lines changed or added

This html diff was produced by rfcdiff 1.48.