Traffic Steering using BGP Flowspec with SRv6 Policy
draft-jiang-idr-ts-flowspec-srv6-policy-03
Network Working Group W. J
Internet-Draft Y. Liu
Intended status: Informational China Mobile
Expires: August 26, 2021 S. Chen
Huawei
February 22, 2021
Traffic Steering using BGP Flowspec with SRv6 Policy
draft-jiang-idr-ts-flowspec-srv6-policy-03
Abstract
BGP Flow Specification (FlowSpec) [I-D.ietf-idr-rfc5575bis] has been
proposed to distribute BGP FlowSpec NLRI to FlowSpec clients to
mitigate (distributed) denial-of-service attacks, and to provide
traffic filtering in the context of a BGP/MPLS VPN service.
Recently, traffic steering applications in the context of SRv6 using
FlowSpec aslo attract attention. This document introduces the usage
of BGP FlowSpec to steer packets into an SRv6 Policy.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
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 August 26, 2021.
J, et al. Expires August 26, 2021 [Page 1]
Internet-Draft FlowSpec with SRv6 Policy February 2021
Copyright Notice
Copyright (c) 2021 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 Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Definitions and Acronyms . . . . . . . . . . . . . . . . . . 3
3. Operations . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Application Example . . . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
9.1. Normative References . . . . . . . . . . . . . . . . . . 6
9.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
Segment Routing IPv6 (SRv6) is a protocol designed to forward IPv6
data packets on a network using the source routing model. SRv6
enables the ingress to add a segment routing header (SRH) [RFC8754]
to an IPv6 packet and push an explicit IPv6 address stack into the
SRH. After receiving the packet, each transit node updates the IPv6
destination IP address in the packet and segment list to implement
hop-by-hop forwarding.
SRv6 Policy [I-D.ietf-spring-segment-routing-policy] is a tunneling
technology developed based on SRv6. An SRv6 Policy is a set of
candidate paths consisting of one or more segment lists, that is,
segment ID (SID) lists. Each SID list identifies an end-to-end path
from the source to the destination, instructing a device to forward
traffic through the path rather than the shortest path computed using
an IGP. The header of a packet steered into an SRv6 Policy is
augmented with an ordered list of segments associated with that SRv6
J, et al. Expires August 26, 2021 [Page 2]
Internet-Draft FlowSpec with SRv6 Policy February 2021
Policy, so that other devices on the network can execute the
instructions encapsulated into the list.
Show full document text