Destination-IP-Community Filter for BGP Flow Specification

Abstract

BGP Flowspec mechanism (BGP-FS) propagates both traffic Flow Specifications and Traffic Filtering Actions by making use of the BGP NLRI and the BGP Extended Community encoding formats. This document specifies a new BGP-FS component type to support community-level filtering. The match field is the community of the destination IP address that is encoded in the Flowspec NLRI. This function is applied in a single administrative domain.¶

1. Introduction

BGP Flow Specification (BGP-FS) [RFC8955] [RFC8956] defines a new BGP NLRI to distribute traffic flow specification rules via BGP ([RFC4271]). BGP-FS policies have a match condition that may be n-tuple match in a policy, and an action that modifies the packet and forwards/drops the packet. Via BGP, new filter rules can be sent to all BGP peers simultaneously without changing router configuration, and the BGP peer can install these routes in the forwarding table. BGP-FS defines Network Layer Reachability Information (NLRI) format used to distribute traffic flow specification rules. NLRI (AFI=1, SAFI=133) is for IPv4 unicast filtering. NLRI (AFI=1, SAFI=134) is for BGP/MPLS VPN filtering.[I-D.ietf-idr-flowspec-l2vpn] extends the flow-spec rules for layer 2 Ethernet packets.¶

This document specifies a new BGP-FS component type to support community-level filtering. The match field is the community of the destination IP address that is encoded in the Flowspec NLRI. This function is applied in a single administrative domain.¶

2. Definitions and Acronyms

• FS: Flow Specification¶

• Destination-IP-Community: The community of the destination IP address¶

3. The Flow Specification Encoding for Destination-IP-Community Filter

This document proposes a new flow specification component type that is encoded in the BGP Flowspec NLRI. The following new component type is defined.¶

• Destination-IP-Community¶

Type TBD1 - Destination-IP-Community¶

Encoding: <type (1 octet), [op, value]+>¶

Contains a set of {operator, value} pairs that are used to match the Destination-IP-Community (i.e. the community of the destination IP address).¶

The operator byte is encoded as:¶

    0   1   2   3   4   5   6   7
  +---+---+---+---+---+---+---+---+
  | e | a |  len  | 0 |lt |gt |eq |
  +---+---+---+---+---+---+---+---+

 Figure 1: Numeric Operator (numeric_op)

Where:¶

e - end-of-list bit. Set in the last {op, value} pair in the list.¶

a - AND bit. If unset, the previous term is logically ORed with the current one. If set, the operation is a logical AND. It MUST be unset in the Destination-IP-Community filter.¶

len - The length of the value field for this operator given as (1 << len). This encodes 1 (len=00), 2 (len=01), 4 (len=10), and 8 (len=11) octets.¶

lt - less than comparison between data and value.¶

gt - greater than comparison between data and value.¶

eq - equality between data and value.¶

The bits lt, gt, and eq can be combined to produce match the Destination-IP-Community filter or a range of Destination-IP-Community filter(e.g. less than community 1 and greater than community 2).¶

The value field is encoded as:¶

   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
  +---------------------------------------------------------------+
  ~          Destination-IP-Community  (4 octets)                 ~
  +---------------------------------------------------------------+

      Figure 2: Destination-IP-Community

Per section 10 of [RFC8955] , If a receiving BGP speaker cannot support this new Flow Specification component type, it MUST discard the NLRI value field that contains such unknown components. Since the NLRI field encoding (Section 4 of [RFC8955]) is defined in the form of a 2-tuple <length, NLRI value>, message decoding can skip over the unknown NLRI value and continue with subsequent remaining NLRI.¶

4. Use Cases

This section describes how to use this function in a simple scenario. Considering the topology shown in Figure 3 ("Comm" is short for "Community"). In AS64597's R1, if the ISP AS64597 wants to redirect all packets originating from IP Prefix 61 to AS64598 and AS64599:¶

"first go to R3", the ISP AS64597 can use the traditional method or the method defining in this draft.¶

                         +---------+
                         | BGP FS  |
                         | Server  |
                         +----|----+
                              |
                              |
                              /
                             /
                ************/************
                *          /            *
  IP Prefix 61  *         / AS64597     *  IP Prefix 81 with Comm 1:1
                *        /              *  IP Prefix 82 with Comm 1:1
   +-------+    *  +---+/        +---+  *   +-------+
   +AS64596+-------+ R1+---------+ R2|------+AS64598+
   +-------+    *  +-+-+\        +---+  */  +-------+
                *        \         |\   /
                *         \        | \ /*
                *          \       |  /\*
                *           \      | /  \  IP Prefix 91 with Comm 1:1
                *            \     |/   *\ IP Prefix 92 with Comm 1:1
                *             \  +-+-+  * \ +-------+
                *              \-+ R3+------+AS64599+
                *                +---+  *   +-------+
                *                       *
                *************************
      Figure 3: Redirect the traffic using Flowspec

Using the traditional method, the ISP AS64597 needs to setup multiple "Destination Prefix + Source Prefix" rules in Router R1 as following:¶

    +--------------+--------------+-------------------------+
    | Destination  | Source Prefix| Redirect to IP Nexthop  |
    | Prefix       |              |                         |
    +--------------+--------------+-------------------------+
    | IP Prefix 81 | IP Prefix 61 |           R3            |
    +--------------+--------------+-------------------------+
    | IP Prefix 82 | IP Prefix 61 |           R3            |
    +--------------+--------------+-------------------------+
    | IP Prefix 91 | IP Prefix 61 |           R3            |
    +--------------+--------------+-------------------------+
    | IP Prefix 92 | IP Prefix 61 |           R3            |
    +--------------+--------------+-------------------------+
    |                  More ...                             |
    +--------------+--------------+-------------------------+

  Figure 4: Using the traditional method to redirect the traffic

Using the method defining in this draft, the ISP AS64597 needs to setup only one "Destination Community + Source Prefix" rule in Router R1 as following:¶

  +--------------+--------------+-------------------------+
  | Destination  | Source Prefix| Redirect to IP Nexthop  |
  | Community    |              |                         |
  +--------------+--------------+-------------------------+
  |     1::1     | IP Prefix 61 |           R3            |
  +--------------+--------------+-------------------------+

  Figure 5: Using the community-level filtering method to redirect the traffic

Obviously, the new method defining in this draft saves a lot of entry spaces on the control plane and forwarding plane, and it would greatly simplify the operation of the control plane, and the more destination prefixes with the same community has, the more obvious the benefit.¶

5. IANA Considerations

IANA is requested to a new entry in "Flow Spec component types registry" with the following values:¶

   +---------+--------------+---------------------------------+
   |   Type  | RFC or Draft |    Description                  |
   +---------+--------------+---------------------------------+
   |   TBD1  |  This Draft  |    Destination-IP-Community     |
   +---------+--------------+---------------------------------+

7. References