]> Huawei

zhangli344@huawei.com

Huawei

jie.dong@huawei.com

Orange

mohamed.boucadair@orange.com

Routing Time-Variant Routing schedule YANG module applicability Time-Variant Routing (TVR) is a routing system that can support the predicted topology changes caused by internal or external reasons. Typical use cases include mobility networks with moving nodes, resource constraints such as power, and tidal traffic demand networks. This document provides examples of how to implement the TVR scheduling capabilities for key use cases. It describes which part of the TVR data model is used and why, and it outlines operational and security considerations when deploying TVR-based technologies.

Introduction The Time-Variant Routing (TVR) Working Group addresses a growing need in modern network environments where predictable variations in topology - such as the restoration, activation, or loss of network elements, are part of normal operations. This approach is essential in dynamic networks with mobile nodes, where links may be frequently disrupted and re-established due to mobility or in networks with highly predictable traffic patterns, where links may be powered down to conserve or reduce energy. This document provides examples of implementing TVR scheduling capabilities in identified use cases. It demonstrates the applicability of the TVR data model, methods for disseminating the TVR schedule, and the necessary IETF ancillary technologies for network environments, such as time synchronization and policy, that support TVR capabilities.

Conventions and Definitions 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 when, and only when, they appear in all capitals, as shown here.

Use Case Examples

Tidal Network Use Case A tidal network is a typical scenario of an Energy Efficient case (). The tidal network means that the volume of traffic in the network changes periodically, like the ocean tide. These changes are mainly affected by human activities. Therefore, this tidal effect is obvious in human-populated areas, such as campuses and airports. In the context of a tidal network, if the network maintains all the devices up to guarantee a maximum throughput all the time, often, power will be wasted on network resources that are not being used. Energy-saving methods may include the deactivation of some or all components of network nodes. These activities have the potential to alter network topology and impact data routing/forwarding in a variety of ways. Interfaces on network nodes can be selectively disabled or enabled based on traffic patterns, thereby reducing the energy consumption of nodes during periods of low network traffic. The following sections will describe how to use the TVR YANG model in Tidal Network.

Applicability of TVR Yang Model in Tidal Network

Network Model According to the description of , the scheduling generation locality and execution locality may be centralized or distributed. When the schedule is generated and executed in a centralized manner and within the same device, the changes are sent to routing applications in wall-clock time via a management interface, which does not need to be delivered by the YANG model. This can be implemented using the existing management plane technology. Therefore, this scenario is outside of the scope of this document. When the schedule is generated and executed in a distributed manner, there is also no need for delivering the schedule by the YANG model. Therefore, this scenario is also outside of the scope of this document. When a schedule is generated in a centralized manner and executed in a distributed manner, the YANG module needs to be used to deliver the schedule to the managed device. Depending on the location of the routing application, the network model can be divided into two types: distributed and centralized.

Centralized Model In the centralized model, the network managing device generates and maintains schedules, the routing application is deployed in the network controller, and the network devices execute the schedules and routing results. The following figure shows the components of the centralized model.

Components of Centralized Model | Network Devices | +----------------------+ +-------------------+ ]]>

Distributed Model In the distributed model, the managing device generates and maintains schedules, the routing application is deployed in the network devices which also executes schedules and route calculation.

Components of Distributed Model

Interaction Between Devices

Centralized Model A centralized model involves the interaction between the managing device and network controller, the managing device and network devices, and the controller and network devices. The managing device needs to deliver node-specific schedules to network devices by TVR Schedule Node YANG module , and the network devices need to report their own status data to the management device. The managing device needs to deliver schedules of the network topology to the network controller by the TVR Network Topology YANG module, so that the routing application in the controller can consider the impact of topology changes on routes when calculating routes. The network controller should deliver the route calculation result to the network devices. The format of the routing results depends on the protocols deployed(The typical protocols include BGP , PCEP, etc.). The routing result for a period of time in the future could be sent to the network devices in wall-clock time or be packed and sent at some special points.

Distributed Model The distributed model only involves the interaction between managing devices and network devices. The managing device must deliver node-specific schedules to network devices by TVR Schedule Node YANG Module and deliver network topology schedules to all the network devices by TVR Network Topology Yang module for route calculation. The network devices must report their status data to the managing device. Editors note: In future versions of this document, we will provide a more detailed procedure for both the distributed and centralized approach.

Encoding of the YANG Model The TVR data model can manage network resources and topologies with scheduled attributes. There are modules defined in the TVR data model, these are:

• The “ietf-tvr-schedule” module contains the schedule YANG definitions. This module uses groupings from data model;
• The “ietf-tvr-topology” module defines a network topology with a time-variant availability schedule;
• The “ietf-tvr-node” module is to be used to manage the scheduled attributes of a single node.

To create a schedule, the following TVR data model objects and subsequent branches are used:

• ‘node-schedule’
• ‘interface-schedule’
• ‘attribute-schedule’

A TVR scenario example is provided below, where a wireless link is shut down for 12 hours, from 19:00 to 7am the next day. The schedule is identified using a unique identifier that is conveyed in ‘schedule-id’, and the recurring schedule can be applied for multiple days using Coordinated Universal Time (UTC). A more detailed example of the json code is provided in this documents Appendix. The methods for disseminating and propagating the generated schedule are discussed in the following subsections.

Management Protocols for TVR The TVR data model is designed to be accessed via YANG-based management protocols such as NETCONF and RESTCONF . This section discusses the applicability of these protocols for configuring time-variant network resources using the TVR YANG data models. NETCONF provides a robust mechanism for managing complex network configurations, particularly when transactional integrity and operational consistency are required. Its ability to execute atomic transactions ensures that schedules involving multiple resources are applied fully, preventing partial updates that could lead to configuration inconsistencies. This feature is important for time-sensitive scheduling in TVR environments. Additionally, NETCONF supports the validation of configurations prior to commitment, allowing operators to verify the correctness of schedules before they are applied. It also includes rollback capabilities, such as restoring a previous configuration during scheduling errors. In contrast, RESTCONF offers a simpler, stateless method for interacting with network devices, making it suitable for use cases requiring lightweight, rapid configuration. RESTCONF utilizes a RESTful interface over HTTP, providing a streamlined approach to network configuration and management. Therefore, RESTCONF may be advantageous in scenarios where quick adjustments to schedules are needed or where integration with web-based or cloud-native systems is a priority. Depending on the type of node in the TVR network, NETCONF would be the preferred protocol for large-scale, critical scheduling operations requiring validation and rollback mechanisms. For smaller-scale or isolated scheduling tasks, RESTCONF provides an efficient and straightforward option without the need for the transactional features offered by NETCONF. The choice of protocol to use with the TVR YANG model should be driven by the specific requirements of the network environment and the complexity of the scheduling tasks involved. The security aspects of both NETCONF and RESTCONF, including their strengths and weaknesses, are discussed further in of this document.

Time Synchronization According to , no matter whether the schedules are executed in a centralized or distributed mode, a mechanism is required to keep the time synchronization between different devices. Different time-variant scenarios may require different granularities of time synchronization. For example, the period of traffic and topology changes in tidal networks is usually a day or week. Therefore, a second-level time synchronization is enough. Existing clock synchronization protocols can be classified into hardware-based protocols and software-based protocols. Hardware-based protocols often rely on dedicated hardware to ensure clock synchronization, such as Global Positioning System (GPS) and Precision Time Protocol (PTP). Software-based protocols, on the other hand, synchronize clocks through software packages running on systems, such as Network Time Protocol (NTP) and Simple Network Time Protocol (SNTP) . Hardware-based protocols typically have higher precision and stability, but also have higher cost due to the dedicated Hardware. Software-based protocols are simple and applicable to common hardware devices, but have lower precision (For example, the NTP can realize the synchronization at tens of milliseconds level). The software-based protocols are appropriate for most of the TVR use cases.

NTP NTP is fundamental for ensuring that TVR mechanisms, which depend on highly accurate timing, function as intended across an entire network. Misalignment in time could lead to serious routing issues, including inefficiency in path forwarding, instability in routing tables, and traffic outages. NTP will be used to ensure:

• Coordination of Planned Network Events;
• Verification of TVR Data Model Time Stamps
• Accurate Scheduling of Paths;
• Fault Tolerance.

NTP uses a hierarchical structure of time sources. Each level of this hierarchy is termed a stratum. Generally, an NTP server synchronized to an authoritative clock runs at stratum 1. Such NTP server functions as the primary time server to provide clock synchronization for other devices on the network. Stratum 2 servers obtain time from stratum 1 servers, stratum 3 servers obtain time from stratum 2 servers, and so on. In TVR use cases, the managing device functions as a level-1 NTP server and synchronized to an authoritative clock source. The network controller and network devices behave as clients to obtain accurate time from the managing device. shows an NTP deployment scenario for obtaining clock from a GPS clock source.

Deployment Case of NTP in Tidal Networks

SNTP SNTP is a subset of the NTP used to synchronize computer clocks in the Internet. It simplifies the complex NTP synchronization function and is suitable for networks with limited resources and loose precision requirements. Compared with NTP, SNTP has lower clock precision, but the synchronization precision still can be guarded under seconds. Therefore, SNTP also meets the time synchronization requirements of tidal networks and can be used as an alternative clock synchronization protocol.

Schedule Database The schedule database is used to store and maintain schedules, the database may be deployed on a managing device and managed devices based on requirements. The schedule source of the schedule database may be diversified, for example, configuration from an administrator or YANG model from the management interface. The schedule entries of different databases may be different, but the content of the same schedule entry in the schedule databases of different devices in the same domain must be consistent. There are at least two ways to make the content of the same schedule entry in different schedule databases consistent:

• All the schedule entries are generated at a specific device;
• Schedule entries are generated at different devices, but there is a synchronization mechanism to synchronize the schedule databases among devices.

Option 1 is simplest and easy to implement. In a time-variant domain, the managing device may receive scheduling requests and generate all schedule entries. Then the schedule entries are delivered to the necessary network devices in the domain through the TVR YANG model. Option 2 relies on advertisement mechanisms (such as routing techniques) to advertise the scheduling data generated by itself to other devices. This could be achieved using extensions to existing routing schemes and techniques. These options will be discussed with the TVR Working Group, and agreed approaches will be documented in future versions of this Internet Draft.

Data Structure defines a TVR Node and TVR Topology YANG modules. The Node YANG module includes node power schedule and interface schedule. The Topology YANG module includes nodes schedule and links schedule. Based on the preceding four schedule types, the schedule database should contain four types of schedule entries in different formats:

• Node power schedule entry;
• Interface schedule entry;
• Node schedule entry;
• Links schedule entry;

The detailed format and fields of different types of schedule entries could reference to the definitions of the corresponding YANG modules. Editors note: Code examples will be provided here in future versions of this document.

Schedule Operations This section provides general requirements for using the TVR schedule. The schedule database should support the add, update, and delete operations. When adding or updating a schedule entry, the execution node needs to check whether resource conflicts exist between the current schedule and existing schedules. If a conflict exists, the operation should be failed. Schedules are updated and deleted based on schedule IDs. Therefore, schedule IDs must be unique in a time-variant domain. This can be handled, e.g., by a dedicated allocation agent within the time-variant domain. Editors note: Future versions of this document will expand on the schedule operations requirements and best practices.

Operational Considerations Several operational considerations exist when using TVR techniques and data models in a network. This section provides some high-level observations and more detailed sub-sections for specific consideration related to schedule dissemination, execution, and recovery in case of failure to apply a schedule or partial change.

• Coordinated Network Events: TVR often coordinates routing changes anticipating events like predictable low-traffic periods or link downtimes (e.g., scheduled maintenance or traffic demand).
• Accurate Scheduling of Paths: TVR schedule capable routers and network nodes will dynamically adjust forwarding paths based on planned changes in link availability or network conditions.
• Time-Stamped Data Models: TVR will require the use time-stamped data models (e.g., schedules for link changes or availability windows) to make interface management decisions. This ensures that all TVR nodes interpret the timing of events consistently and implement time-based policies correctly.

Therefore, network time accuracy and time-stamped data models are critical to ensure that coordinated network events and scheduled path decisions across the network are based on a consistent time reference. Without accurate time sync, nodes could apply different schedules, causing routing inconsistencies, path flapping, or packet loss.

Schedule Execution Consideration Schedules execution means that a component (e.g., device) undertakes an action (e.g., allocates and deallocates resources) at specified time points. In a tidal network, the schedule execution indicates powering on/off specific network components (such as interfaces or entire network devices) directly or by commands. The schedule executor should understand the consequences of the schedule execution. The power on/off of network components usually affects the network topology, the addition and deletion of the topology need to be considered separately. A link coming up or a node joining a topology should not have any functional change until the change is proven to be fully operational. The routing paths may be pre-computed but should not be installed before all of the topology changes are confirmed to be operational. The benefits of this pre-computation appear to be very small. The network may choose to not do any pre-installation or pre-computation in reaction to topological additions at a small cost of some operational efficiency. Topological deletions are an entirely different matter. If a link or node is to be removed from the topology, then the network should act before the anticipated change to route traffic around the expected topological change. Specifically, at some point before the planned topology change, the routing paths should be pre-computed and installed before the topology change takes place. The required time to perform such planned action will vary depending on the exact network and configuration. When using an IGP or other distributed routing protocols, the affected links may be set to a high metric to direct traffic to alternate paths. This type of change does require some time to propagate through the network, so the metric change should be initiated far enough in advance that the network converges before the actual topological change. Editor's Note: multi-manager scenarios need to be considered.

Security Considerations The integration of time-variant mechanisms in network operations presents distinct security challenges that require thorough analysis to safeguard the network’s integrity, availability, and confidentiality. Networks that rely on time-sensitive data for routing and forwarding decisions are particularly susceptible to attacks that exploit timing dependencies. The "Security Considerations" section of outlines various threat vectors and categories specific to time-variant environments. In this document, a tidal demand use case has been presented, highlighting the need for robust security measures in the processes of generating, disseminating, and applying schedules to control tidal interfaces. It is essential to assess security risks and implement mitigation strategies to ensure the security of both the network and individual nodes throughout the scheduling process. Future iterations of this document will provide detailed security techniques and best practices to address these challenges.

IANA Considerations This document has no IANA actions.

References Normative References In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. Futurewei Technologies LabN Consulting, L.L.C. LabN Consulting, L.L.C. LabN Consulting, L.L.C. Viagenie The YANG model in this document includes three modules, and can be used to manage network resources and topologies with scheduled attributes, such as predictable link loss and link connectivity as a function of time. The intent is to have this information be utilized by Time-Variant Routing systems. Informative References JHU/APL Thales Alenia Space Futurewei Technologies Ori Industries Huawei This document introduces use cases where Time-Variant Routing (TVR) computations (i.e. routing computations taking into considerations time-based or scheduled changes to a network) could improve routing protocol convergence and/or network performance. Lancaster University Telefonica JHU/APL Huawei Time-Variant Routing (TVR) refers to calculating a path or subpath through a network where the time of message transmission (or receipt) is part of the overall route computation. This means that, all things being equal, a TVR computation might produce different results depending on the time that the computation is performed without other detectable changes to the network topology or other cost functions associated with the route This document introduces requirements where TVR computations could improve message exchange in a network. Huawei Huawei Orange Lancaster University This document defines a common schedule YANG module which is designed to be applicable for scheduling purposes such as event, policy, services, or resources based on date and time. For the sake of better modularity, the module includes a set of recurrence related groupings with varying granularity levels (i.e., from basic to advanced). The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK] This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF). The Network Time Protocol (NTP) is widely used to synchronize computer clocks in the Internet. This document describes NTP version 4 (NTPv4), which is backwards compatible with NTP version 3 (NTPv3), described in RFC 1305, as well as previous versions of the protocol. NTPv4 includes a modified protocol header to accommodate the Internet Protocol version 6 address family. NTPv4 includes fundamental improvements in the mitigation and discipline algorithms that extend the potential accuracy to the tens of microseconds with modern workstations and fast LANs. It includes a dynamic server discovery scheme, so that in many cases, specific server configuration is not required. It corrects certain errors in the NTPv3 design and implementation and includes an optional extension mechanism. [STANDARDS-TRACK] This memorandum describes the Simple Network Time Protocol Version 4 (SNTPv4), which is a subset of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. SNTPv4 can be used when the ultimate performance of a full NTP implementation based on RFC 1305 is neither needed nor justified. When operating with current and previous NTP and SNTP versions, SNTPv4 requires no changes to the specifications or known implementations, but rather clarifies certain design features that allow operation in a simple, stateless remote-procedure call (RPC) mode with accuracy and reliability expectations similar to the UDP/TIME protocol described in RFC 868. This memorandum obsoletes RFC 1769, which describes SNTP Version 3 (SNTPv3), and RFC 2030, which describes SNTPv4. Its purpose is to correct certain inconsistencies in the previous documents and to clarify header formats and protocol operations for NTPv3 (IPv4) and SNTPv4 (IPv4, IPv6, and OSI), which are also used for SNTP. A further purpose is to provide guidance for home and business client implementations for routers and other consumer devices to protect the server population from abuse. A working knowledge of the NTPv3 specification, RFC 1305, is not required for an implementation of SNTP. This memo provides information for the Internet community.

Acknowledgments TODO acknowledge.

Appendix A: Code Examples

Code Examples for Tidal Network Tidal networks usually need to manage the availability of some node or interfaces. shows the example of a scheduling node that is powered on from 12 AM, December 1, 2025 to 12 AM, December 1, 2026 in UTC and its interface named "interface1" is scheduled to be enabled at 7:00 AM and disabled at 1:00 AM, every day, from December 1, 2025 to December 1, 2026 in UTC. The JSON encoding is used only for illustration purposes.

An Example of Interface Activation Scheduling

Contributors Lancaster University

United Kingdom d.king@lancaster.ac.uk

Lancaster University

c.rotsos@lancaster.ac.uk

China Mobile

liupengyjy@chinamobile.com

Juniper Networks

tony.li@tony.li