| Internet-Draft | BGP FlowSpec Path Scheduling | November 2023 |
| Zhang, et al. | Expires 9 May 2024 | [Page] |
Path scheduling is required in many network scenarios. For example, some links or nodes will be shut down in the tidal network when the traffic decreases, which may lead to the expiration of some routing paths.¶
This document defines a new type of component for BGP Flow Specification to identify the packets arrived at different time slot. Based on that, the headend can steer packets into different paths at different time.¶
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 9 May 2024.¶
Copyright (c) 2023 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.¶
[RFC8955] and [RFC8956] define the BGP [RFC4271] Flow Specification (FlowSpec) that allows conveying flow specifications and traffic Action/Rules associated. BGP Flow specifications are encoded within the MP_REACH_NLRI and MP_UNREACH_NLRI attributes [RFC4760]. Rules (Actions associated) are encoded in Extended Community attribute [RFC4360].¶
The existing traffic filter rules and actions in FlowSpec are always effective and will steer specific traffic into one path once been delivered to the headend. However, there are many scenarios that need to schedule routing paths in the network.¶
[I-D.zzd-tvr-use-case-tidal-network] introduces the tidal network, in which the topology of the network will change periodically over time. The topology change may cause some of the paths invalid, and lead to path reselection or even recalculation. However, the reselection or recalculation takes a period of time, which will affect packet forwarding and cause problems such as packet disorder and packet loss. On a network with predictable topology changes, the controller knows future topology changes, it can deliver a FlowSpec to the headend which can steers traffic to different paths in advance to prevent packet forwarding from being affected by topology changes.¶
This document defines a new type of component for BGP Flow Specification to identify the packets arrived at different time slot. Based on that, the headend can steer packets into different paths at different time.¶
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.¶
[I-D.zzd-tvr-use-case-tidal-network] introduces the time variant routing scenario in the tidal network, in which the traffic volume varies greatly at different time. In order to reduce the power consumption, some of the links and nodes may be shut down when the traffic is at a low level.¶
In this scenario, the controller can generate a FlowSpec with shceduling time rule to identify the packets arrivaling time and corresponding paths. The headend doesn’t need to wait for the advertisement of topology change and just steer traffic in to different pathes based on the flowSpec with scheduling time information, the affection of topology change is minimized.¶
[RFC8955] defines 12 Components to identify different traffics. Based on [RFC8955], this document defines a new Component to identify the arrival time of packets, so as to enable path scheduling.¶
Encoding: <type (1 octet), length (1 octet), scheduling time information (variabile)]+>¶
Defines the time information that matches the arrival time of packets. This component matches if either the arrival time of an IP packet in the scope of scheduling time information.¶
The Scheduling time information has two formats according to the change regularity of network topology. They are Aperiodic Scheduling Time Information (ASTI) and Periodic Scheduling Time Information (PSTI).¶
The ASTI indicates one or more group of matching time slot (each includes the enable time and disable time) for the packets. The format of ASTI 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Enable Time | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Disable Time | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | / Variable / | |
Type: used to identify the type of scheduling time information. The value and corresponding types are shown as follows:¶
| Value | Type |
|---|---|
| 0x01 | Aperiodic Scheduling Time Information |
| 0x02 | Periodic Scheduling Time Information |
Enable Time: the time in seconds indicates the start time when the packets matching.¶
Disable Time: the time in seconds indicates the end time when the packets matching.¶
Variable: one or more groups of time information (A information group is composed of Enable Time and Disable time) may be included in one ASTI.¶
The PSTI indicates one or more group of periodic matching time slot (each includes period, enable time and disable time) for the packets. The format of PSTI 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Period | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Enable Time | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Disable Time | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | / Variable / | |
Type: as defined in clause “Aperiodic Scheduling Time Information”¶
Length: the size of the value field in octets.¶
Period: the time in seconds between the enable time of one repetition and the enable time of the next repetition.¶
Enable Time: the time in seconds indicates when the path(s) is(are) enabled.¶
Disable Time: the time in seconds indicates when the path(s) is(are) disabled¶
Variable: one or more groups of time information(A information group is composed of Period, Enable Time and Disable time) may be included in one PSTI.¶
When the headend device (as a FlowSpec client) receives a instruction with scheduling time information from a BGP FlowSpec Controller, it will steer the traffic packets matching the time slot and other conditions in the Flowspec instruction into a specific path.¶
These extensions to BGP FlowSpec do not add any new security issues to the existing protocol.¶
This document defines a new Component in the registry " Flow Spec Component Types" to be assigned by IANA:¶
| Value | Description | Reference |
|---|---|---|
| TBD1 | Scheduling Time Information | This document |