Destination-IP-Origin-AS Filter for BGP Flow Specification
draft-wang-idr-flowspec-dip-origin-as-filter-02

Document Type Active Internet-Draft (individual)
Last updated 2020-03-09
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized 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)
Network Working Group                                            H. Wang
Internet-Draft                                                    Huawei
Intended status: Standards Track                                 A. Wang
Expires: September 10, 2020                                China Telecom
                                                               S. Zhuang
                                                                  Huawei
                                                          March 09, 2020

       Destination-IP-Origin-AS Filter for BGP Flow Specification
            draft-wang-idr-flowspec-dip-origin-as-filter-02

Abstract

   BGP Flowspec mechanism [RFC5575] [I-D.ietf-idr-rfc5575bis] propogates
   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 AS-level filtering.  The match field is the origin AS number
   of the destination IP address that is encoded in the Flowspec NLRI.

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 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 September 10, 2020.

Wang, et al.           Expires September 10, 2020               [Page 1]
Internet-Draft       Destination-IP-Origin-AS Filter          March 2020

Copyright Notice

   Copyright (c) 2020 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.  The Flow Specification Encoding for Destination-IP-Origin-AS
       Filter  . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Use Case  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   6.  IANA  . . . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   6
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   BGP Flow Specification (BGP-FS) [RFC5575] [I-D.ietf-idr-rfc5575bis]
   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][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 AS-
   level filtering.  The match field is the origin AS number of the
   destination IP address that is encoded in the Flowspec NLRI.

Wang, et al.           Expires September 10, 2020               [Page 2]
Internet-Draft       Destination-IP-Origin-AS Filter          March 2020

2.  Definitions and Acronyms

   o  FS: Flow Specification
Show full document text