BGP Flow Specification for SRv6
draft-li-idr-flowspec-srv6-01

Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
Stream (None)
Intended RFC status (None)
Formats plain text pdf 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                                              Z. Li
Internet-Draft                                                     L. Li
Intended status: Standards Track                                  Huawei
Expires: May 7, 2020                                             H. Chen
                                                               Futurewei
                                                                C. Loibl
                                               Next Layer Communications
                                                                  Y. Zhu
                                                           China Telecom
                                                                  L. Liu
                                                                 Fujitsu
                                                                  X. Liu
                                                          Volta Networks
                                                        November 4, 2019

                    BGP Flow Specification for SRv6
                     draft-li-idr-flowspec-srv6-01

Abstract

   This draft proposes extensions to BGP to distribute traffic Flow
   Specifications for SRv6 for filtering SRv6 packets that match a
   sequence of conditions.

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 May 7, 2020.

Li, et al.                 Expires May 7, 2020                  [Page 1]
Internet-Draft       BGP Flow Specification for SRv6       November 2019

Copyright Notice

   Copyright (c) 2019 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 SRv6  . . . . . . . . . .   4
     3.1.  Type TBD1 - Whole SID . . . . . . . . . . . . . . . . . .   4
     3.2.  Type TBD2 - Some bits of SID  . . . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   5.  IANA  . . . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   BGP Flow Specification (BGP-FS) [RFC5575] defines a new BGP NLRI to
   distribute a flow specification, which is an n-tuple comprising a
   sequence of matching criteria that can be applied to IP traffic.  It
   defines a minimum set of filtering actions as BGP extended community
   values [RFC4360] that modify the traffic packet and forwards/drops
   the packet.  [I-D.ietf-idr-rfc5575bis] gives more details about them.
   The NLRI (AFI=1, SAFI=133) is for IPv4 unicast flow specification and
   NLRI (AFI=1, SAFI=134) is for BGP/MPLS VPNv4 flow specification.
   [I-D.ietf-idr-flow-spec-v6] redefines the [RFC5575] SAFIs to make
   them AFI specific and applicable to both IPv4 and IPv6 applications.
   [I-D.ietf-idr-flowspec-l2vpn] extends the flow-spec rules for layer 2
   Ethernet packets.

   Segment Routing (SR) for unicast traffic has been proposed to cope
   with the usecases in traffic engineering, fast re-reroute, service
Show full document text