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

Document Type Active Internet-Draft (individual)
Last updated 2019-03-11
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
Network Working Group                                              Z. Li
Internet-Draft                                                     L. Li
Intended status: Standards Track                                  Huawei
Expires: September 12, 2019                               March 11, 2019

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

Abstract

   This draft proposes BGP flow specification rules that are used to
   filter SRv6 packets.

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 12, 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

Li & Li                Expires September 12, 2019               [Page 1]
Internet-Draft       BGP Flow Specification for SRv6          March 2019

   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  . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   5.  IANA  . . . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   BGP Flow Specification (BGP-FS) [RFC5575]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.

   Segment Routing (SR) for unicast traffic has been proposed to cope
   with the usecases in traffic engineering, fast re-reroute, service
   chain, etc.  SR architecture can be implemented over an IPv6 data
   plane using a new type of Segment Routing Header
   (SRH)[I-D.ietf-6man-segment-routing-header] . SRv6 Network
   Programming[I-D.filsfils-spring-srv6-network-programming] defined the
   SRv6 network programming concept and its most basic functions.  SRv6
   SID will have the form LOC:FUNCT:ARGS::.

   LOC: Each operator is free to use the locator length it chooses.
   Most often the LOC part of the SID is routable and leads to the node
   which instantiates that SID

   FUNCT: The FUNCT part of the SID is an opaque identification of a
   local function bound to the SID. (e.g.  End: Endpoint, End.X, End.T,
   End.DX2 etc.)

Li & Li                Expires September 12, 2019               [Page 2]
Internet-Draft       BGP Flow Specification for SRv6          March 2019

   ARGS: A function may require additional arguments that would be
   placed immediately after the FUNCT

   This document specifies a new subset of BGP-FS component types to
Show full document text