Populate to FIB Action for FlowSpec
draft-li-idr-flowspec-populate-to-fib-01

Document Type Active Internet-Draft (individual)
Last updated 2017-07-02
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
IDR                                                                Z. Li
Internet-Draft                                              China Mobile
Updates: 5575 (if approved)                                      J. Dong
Intended status: Standards Track                               S. Zhuang
Expires: January 3, 2018                             Huawei Technologies
                                                            July 2, 2017

                  Populate to FIB Action for FlowSpec
                draft-li-idr-flowspec-populate-to-fib-01

Abstract

   A bit, F bit, is defined in traffic action extended community, which
   is used by FlowSpec to indicate the associated specifications be
   populated in FIB (Forwarding Information Base) after appropriate
   process.

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 [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 http://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 January 3, 2018.

Copyright Notice

   Copyright (c) 2017 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

Li, et al.               Expires January 3, 2018                [Page 1]
Internet-Draft          FlowSpec populate to FIB               July 2017

   (http://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.  Populate to FIB Action  . . . . . . . . . . . . . . . . . . .   3
   3.  Implementation Considerations . . . . . . . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   BGP FlowSpec [RFC5575] provides a flexible mechanism to distribute
   traffic flow specifications, where the matching rules are encoded in
   the Border Gateway Protocol Network Layer Reachability Information
   (BGP NLRI) with defined new format and the corresponding actions are
   encoded in BGP Extended communities.

   In routers, traffic flow specifications distributed by BGP FlowSpec
   [RFC5575] are stored in distinct set of RIBs (Routing Information
   Base) according to their (AFI, SAFI) pairs.  These RIBs are then
   populated to the dedicated hardware (most of them are TCAM based)
   usually shared with ACLs (Access Control Lists).  The dedicated
   hardware is much more expensive and space limited when compared with
   the hardware used to store the FIB (Forwarding Information Base),
   which is usually sufficient to fit several millions of FIB entries.
   Although in some implementations, the hardware used to populate
   traffic flow specifications and FIB entries is the same, the size for
   each parts is fixed at design stage.  As the number of ACL rules and
   FlowSpec specifications increases, especially when FlowSpec is used
   for dynamic traffic flow steering, which is one of the three BGP
   FlowSpec applications listed in [RFC5575] and
   [I-D.ietf-idr-rfc5575bis], hardware space requirement of FlowSpec
   specifications in the field network may exceed the size of the
   dedicated hardware.  To save the limited and expensive space of the
   dedicated hardware, it is better to populate some FlowSpec
   specifications to FIB if possible.  The destination prefix based
Show full document text