IDR L. Zhang, Ed. Internet-Draft T. Zhou Intended status: Standards Track Huawei Expires: 27 April 2027 Z. Li China Mobile J. Dong Huawei 24 October 2026 BGP Flow Specification Extensions for Scheduling draft-zzd-idr-flowspec-scheduling-05 Abstract BGP Flow Specification allows conveying flow specifications and associated traffic actions/rules to perform different actions based on traffic characteristics. Existing traffic filter rules and actions in FSv2 remain effective perpetually; once delivered to the headend, the rules and actions are permanent for traffic. However, some operators wish to perform different actions for specific flows at specific time. This document extends BGP FSv2 with a scheduling time component to match the arrival time of packets. Based on this component, the headend can perform different actions for specific traffic at different times. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 27 April 2027. Zhang, et al. Expires 27 April 2027 [Page 1] Internet-Draft BGP FlowSpec Scheduling October 2026 Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 2. FlowSpecv2 Extensions for Scheduling . . . . . . . . . . . . 3 2.1. Scheduling Time Information . . . . . . . . . . . . . . . 4 3. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.1. Receiving Procedures . . . . . . . . . . . . . . . . . . 5 3.2. Matching Procedures . . . . . . . . . . . . . . . . . . . 6 4. Operational Considerations . . . . . . . . . . . . . . . . . 6 5. Compatibility . . . . . . . . . . . . . . . . . . . . . . . . 6 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 8.1. Normative References . . . . . . . . . . . . . . . . . . 7 8.2. Informative References . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 1. Introduction [RFC8955] and [RFC8956] define BGP [RFC4271] Flow Specification (FSv1), which allows conveying flow specifications and associated traffic actions/rules. BGP FlowSpec rules are encoded within the MP_REACH_NLRI and MP_UNREACH_NLRI attributes [RFC4760]. Associated actions are encoded in Extended Community attributes [RFC4360]. FSv2[I-D.ietf-idr-fsv2-ip-basic] is an update of FSv1, it addresses the issues collected during the deployment of FSv1 and provides flexible TLV-based encoding. Existing traffic filter rules and actions in FSv2 remain effective perpetually; once delivered to the headend, the rules and actions are permanent for traffic. However, some operators wish to perform different actions for specific flows at specific time. Zhang, et al. Expires 27 April 2027 [Page 2] Internet-Draft BGP FlowSpec Scheduling October 2026 In tidal networks such as IP carrier backbone networks, traffic varies periodically. Traffic surges during daily rush hours (typically 20:00–22:00) may lead to congestion on certain links. To mitigate such peak-time congestion, operators wish to divert some traffic onto alternative paths or limit the rate of selected flows, with these policies required to be automatically enabled and disabled at specified times. This document extends BGP FSv2 with a scheduling time component to match the arrival time of packets. Based on this component, the headend can perform different actions for specific traffic at different times (e.g., diverting traffic to different paths). 1.1. Requirements Language 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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. 2. FlowSpecv2 Extensions for Scheduling In Section 3.1.1 of [I-D.ietf-idr-fsv2-ip-basic], it defines a list of FSv2 filter family types, including the value 200 assigned for the time filter family type. The format of time filter is shown below: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | FSv2 Filter Family type =200 | Fsv2 filter Family length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | FSv2 Filter Component TLVs (variable) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: Format of time filter in FSv2 This document defines a new FSv2 filter component, the scheduling time component, for the FSv2 time filter family. It matches packet arrival times to trigger specific actions. The value 100 is recommended as the type value for the scheduling time component. Encoding: Zhang, et al. Expires 27 April 2027 [Page 3] Internet-Draft BGP FlowSpec Scheduling October 2026 Scheduling time information: time criteria used to filter packets, contains a list of Scheduling Time information. The format of scheduling time information is specified in Section 2.1. 2.1. Scheduling Time Information The format of scheduling time information is shown as follows: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Schedule-id | Length | Flags |P|S| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Start Time | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Start Time | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | End Time (Duration) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | End Time (Duration) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Frequency (Optional) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Recurrence Count(Optional) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 2: Format of Scheduling Time Information * Schedule-id: 8-bit value, a unique identifier to distinguish each schedule within a Filter Component. This value is allocated by the FlowSpec originator. * length: 8 bits, length of the current scheduling time information in bytes. * Flags: 8 bits. Currently only 2 bits are defined; remaining bits are reserved. The reserved bit should be set to 0 and ignored by the receiver. - P (Period format): 1-bit flag indicating the interpretation of the period definition. If P=1, the period is defined by a start time field and an end time field. If P=0, the period is defined by a start time field plus a duration value. Zhang, et al. Expires 27 April 2027 [Page 4] Internet-Draft BGP FlowSpec Scheduling October 2026 - S (Schedule type): 1-bit flag indicating the schedule recurrence type. If S=0, the schedule has only one instance; the Frequency and Recurrence Count fields MUST NOT be present in the sub-TLV. If S=1, the schedule has multiple recurring instances; the Frequency and Recurrence Count fields MUST be present. * Start Time: 64-bit value, representing the number of seconds since the epoch. It specifies the start time for traffic matching. The epoch is 1 January 1970 at 00:00 UTC. * End Time (Duration): 64-bit value. If flag P=1, this field specifies the endtime for traffic matching. If flag P=0, this field carries the number of seconds offset from the Start Time and specifies the duration of traffic matching. * Frequency (optional): 32-bit value. It defines the number of seconds between the start time of one schedule instance and the start time of the next instance. This field indicates the recurrence interval for all instances of this schedule. This field MUST NOT be present if S=0. * Recurrence Count (optional): 32-bit value, specifying the total number of repetitions. For example, if set to 2, the schedule repeats twice using the specified Frequency. This field MUST NOT be present if S=0. Value of 0 means repeat infinitely. Multiple instances of Scheduling Time Information may occur in a scheduling time component TLV. Multiple Scheduling Time Information within the same time component are OR'ed. if any time window matches the packet arrival time, the Time Filter matches. 3. Procedures 3.1. Receiving Procedures When a BGP speaker receives a FSv2 NLRI containing a Scheduling Time Component in the Time Filter Family (type 200): * It validates each scheduling time information in the Scheduling Time Component TLV. Invalid scheduling time information in the component (e.g., inconsistent S flag and optional fields, EndTime ≤ StartTime) SHOULD be silently discarded (other scheduling time information within the same component still valid). If all scheduling time information in the component are invalid, the entire Time Filter is considered not matching. Zhang, et al. Expires 27 April 2027 [Page 5] Internet-Draft BGP FlowSpec Scheduling October 2026 * The speaker installs the FlowSpec rule into the local policy. The rule is persistent in the BGP RIB until receiving a explicit withdrawn. * The forwarding plane evaluates packet arrival time against the scheduling time component. * Other FSv2 filter families in the same NLRI are AND'ed with the Time Filter result. 3.2. Matching Procedures A packet matches this FlowSpec rule if and only if: * All non-Time filter families match; AND * At least one valid Scheduling Time Information in the Scheduling time Component matches the packet arrival UTC time. * When the time windows of a scheduling time component expire, the filter will stop matching incoming packets. The expiration will NOT trigger automatic BGP withdrawal until the corresponding explict withdrawal is received. 4. Operational Considerations All headend nodes executing scheduling FlowSpec rules with a time filter MUST be synchronized to a common UTC time source. Synchronization loss may cause unexpected action execution, even leading to packet loss. The controller originating these FlowSpec NLRI is responsible for converting operator local-time schedules into UTC epoch timestamps. Forwarding nodes only process UTC timestamps and have no awareness of local time zones. A large number of time filters will increase forwarding-plane matching state and CPU overhead for time-window evaluation. Operators SHOULD limit the numbers of time filters on device. 5. Compatibility According to the description in Section 3.2 of [I-D.ietf-idr-fsv2-ip-basic], BGP speakers that implement FSv2 but do NOT support the Time Filter Family or the Scheduling Time Component will check the syntax, but do not handle the semantic meaning unknown filter component. Zhang, et al. Expires 27 April 2027 [Page 6] Internet-Draft BGP FlowSpec Scheduling October 2026 Existing FSv2 NLRIs without the time filter family are unaffected by this extension. 6. Security Considerations BGP Flow Specification inherits the security properties of BGP, including risks of route hijacking, malicious NLRI injection, and tampering of flow rules. The extensions defined in this document add time-based matching criteria to FlowSpec rules and do not introduce fundamentally new security classes of threats. Existing security best practices for BGP FlowSpec [RFC8955] and [I-D.ietf-idr-fsv2-ip-basic] remain fully applicable. 7. IANA Considerations IANA is requested to create a new registry named "Flow Specification v2 Time Component Types". Within this registry, IANA is requested to assign type value 100 for the Scheduling Time Component: +======+===========================+===============+ | Type | Description | Reference | +======+===========================+===============+ | 0 | Reserved | This document | +------+---------------------------+---------------+ | 1-99 | Unassigned | This document | +------+---------------------------+---------------+ | 100 | Scheduling Time Component | This document | +------+---------------------------+---------------+ Table 1 8. References 8.1. Normative References [RFC8955] Loibl, C., Hares, S., Raszuk, R., McPherson, D., and M. Bacher, "Dissemination of Flow Specification Rules", RFC 8955, DOI 10.17487/RFC8955, December 2020, . [RFC8956] Loibl, C., Ed., Raszuk, R., Ed., and S. Hares, Ed., "Dissemination of Flow Specification Rules for IPv6", RFC 8956, DOI 10.17487/RFC8956, December 2020, . Zhang, et al. Expires 27 April 2027 [Page 7] Internet-Draft BGP FlowSpec Scheduling October 2026 [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, "Multiprotocol Extensions for BGP-4", RFC 4760, DOI 10.17487/RFC4760, January 2007, . [I-D.ietf-idr-fsv2-ip-basic] Hares, S., Eastlake, D. E., Dong, J., Yadlapalli, C., Maduschke, S., and J. Haas, "BGP Flow Specification Version 2 - for Basic IP", Work in Progress, Internet- Draft, draft-ietf-idr-fsv2-ip-basic-08, 28 September 2026, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . 8.2. Informative References [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, DOI 10.17487/RFC4271, January 2006, . [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended Communities Attribute", RFC 4360, DOI 10.17487/RFC4360, February 2006, . Authors' Addresses Li Zhang (editor) Huawei Beiqing Road Beijing China Email: zhangli344@huawei.com Tianran Zhou Huawei Email: zhoutianran@huawei.com Zhang, et al. Expires 27 April 2027 [Page 8] Internet-Draft BGP FlowSpec Scheduling October 2026 Zhenqiang Li China Mobile Email: lizhenqiang@chinamobile.com Jie Dong Huawei Email: jie.dong@huawei.com Zhang, et al. Expires 27 April 2027 [Page 9]