Appendix C. Examples of Using the "ietf-schedule" Module for Scheduled Use of Resources Framework

Dieser Abschnitt bewahrt den RFC-Text zum ietf-schedule YANG model, einschliesslich recurrence groupings, iCalendar-like rules, schedule status groupings, DISMAN-SCHEDULE-MIB relationship, IANA registrations, YANG/XML examples und scheduled resource examples.

Originaler RFC-Text

Appendix C.  Examples of Using the "ietf-schedule" Module for Scheduled
             Use of Resources Framework

   This section exemplifies how the architecture for supporting
   scheduled reservation of Traffic Engineering (TE) resources in
   [RFC8413] might leverage the "period-of-time" grouping defined in the
   "ietf-schedule" module to implement scheduled use of resources.

   The following example module shows how a scheduled link capacity
   reservation could be defined.

   module example-sch-capacity-res {
     yang-version 1.1;
     namespace "http://example.com/example-sch-capacity-res";
     prefix "ex-schecaparev";

     import ietf-network-topology {
       prefix "nt";
     }

     import ietf-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 {
       description
         "A container for a scheduled link capability reservations.";
       list scheduled-link-capacity {
         key "schedule-id";
         description
           "Definition of scheduled link capacity list.";
         leaf schedule-id {
           type string;
           description
             "The schedule identifier for this schedule rule.";
         }
         leaf link-id {
           type nt:link-id;
           description
             "The identifier of a link in the topology.";
         }
         leaf reserved-capability {
           type uint64;
           units "Mbps";
           description
             "The reserved capability for a particular link.";
         }
         uses schedule:period-of-time;
       }
     }
   }

   Section 4 of [RFC8413] defines the reference architecture for
   scheduled use of resources.  The service requester sends a request to
   a Path Computation Element (PCE) and includes the parameters of the
   Label Switched Path (LSP) that the requester wishes to supply.  The
   configuration example to provide the scheduled resource is shown in
   Figure 25.

   <?xml version="1.0" encoding="utf-8"?>
   <link-capability-reservations
     xmlns="http://example.com/example-sch-capacity-res"
     xmlns:schedule="urn:ietf:params:xml:ns:yang:ietf-schedule">
      <scheduled-link-capacity>
         <schedule-id>1</schedule-id>
         <link-id>1-2-1</link-id>
         <reserved-capability>500</reserved-capability>
         <period-start>2025-03-10T08:00:00Z</period-start>
         <period-end>2025-03-10T09:00:00Z</period-end>
      </scheduled-link-capacity>
      <scheduled-link-capacity>
         <schedule-id>2</schedule-id>
         <link-id>2-1-1</link-id>
         <reserved-capability>400</reserved-capability>
         <period-start>2025-04-01T00:00:00Z</period-start>
         <duration>PT09:00:00</duration>
      </scheduled-link-capacity>
      <scheduled-link-capacity>
         <schedule-id>3</schedule-id>
         <link-id>2-1-1</link-id>
         <reserved-capability>500</reserved-capability>
         <period-start>2025-04-01T09:00:00Z</period-start>
         <period-end>2025-04-01T23:59:59Z</period-end>
      </scheduled-link-capacity>
   </link-capability-reservations>

        Figure 25: Example of Scheduled Link's Bandwidth Reservation