Carrying Label Information for BGP FlowSpec
draft-ietf-idr-bgp-flowspec-label-01

Document Type Active Internet-Draft (idr WG)
Last updated 2016-12-06
Stream IETF
Intended RFC status (None)
Formats plain text pdf xml html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Idr Working Group                                               Q. Liang
Internet-Draft                                                  S. Hares
Intended status: Standards Track                                  J. You
Expires: June 9, 2017                                             Huawei
                                                               R. Raszuk
                                                                  Nozomi
                                                                   D. Ma
                                                           Cisco Systems
                                                        December 6, 2016

              Carrying Label Information for BGP FlowSpec
                  draft-ietf-idr-bgp-flowspec-label-01

Abstract

   This document specifies a method in which the label mapping
   information for a particular FlowSpec rule is piggybacked in the same
   Border Gateway Protocol (BGP) Update message that is used to
   distribute the FlowSpec rule.  Based on the proposed method, the
   Label Switching Routers (LSRs) (except the ingress LSR) on the Label
   Switched Path (LSP) can use label to indentify the traffic matching a
   particular FlowSpec rule; this facilitates monitoring and traffic
   statistics for FlowSpec rules.

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 June 9, 2017.

Liang, et al.             Expires June 9, 2017                  [Page 1]
Internet-Draft                BGP FlowSpec                 December 2016

Copyright Notice

   Copyright (c) 2016 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
   (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
     1.1.  Background  . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  MPLS Flow Specification Deployment  . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Overview of Proposal  . . . . . . . . . . . . . . . . . . . .   4
   4.  Protocol Extensions . . . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security considerations . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   This section provides the background for proposing a new action for
   BGP Flow specification that push/pops MPLS or swaps MPLS tags.  For
   those familiar with BGP Flow specification ([RFC5575], [RFC7674],
   [I-D.ietf-idr-flow-spec-v6], [I-D.ietf-idr-flowspec-l2vpn],
   [I-D.ietf-idr-bgp-flowspec-oid] and MPLS ([RFC3107]) can skip this
   background section.

   [I-D.hr-idr-rfc5575bis] provides updates to [RFC5575] to resolve
   unclear sections in text and conflicts with interactions of filtering
   actions.

Liang, et al.             Expires June 9, 2017                  [Page 2]
Internet-Draft                BGP FlowSpec                 December 2016
Show full document text