BGP FlowSpec Extensions for Routing Policy Distribution (RPD)
draft-li-idr-flowspec-rpd-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-07-06
Stream (None)
Intended RFC status (None)
Formats 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                                       Huawei Technologies
Intended status: Standards Track                                   L. Ou
Expires: January 7, 2016                                          Y. Luo
                                                  China Telcom Co., Ltd.
                                                               S. Zhuang
                                                                   N. Wu
                                                     Huawei Technologies
                                                           July 06, 2015

     BGP FlowSpec Extensions for Routing Policy Distribution (RPD)
                      draft-li-idr-flowspec-rpd-00

Abstract

   This document describes a mechanism to use BGP Flowspec address
   family [RFC5575] as routing-policy distribution protocol.  This
   mechanism is called BGP FlowSpec Extensions for Routing Policy
   Distribution (BGP FS RPD).

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 RFC 2119 [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 7, 2016.

Li, et al.               Expires January 7, 2016                [Page 1]
Internet-Draft                 BGP FS RPD                      July 2015

Copyright Notice

   Copyright (c) 2015 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.  Routing Policies  . . . . . . . . . . . . . . . . . . . .   3
     1.2.  BGP FlowSpec  . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  BGP FlowSpec Extensions for Routing Policy Distribution .   4
   2.  Definitions and Acronyms  . . . . . . . . . . . . . . . . . .   5
   3.  Protocol Extensions . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  FlowSpec Traffic Actions for Routing Policy Distribution    5
     3.2.  BGP Policy Attribute  . . . . . . . . . . . . . . . . . .   6
       3.2.1.  Match Fields Format . . . . . . . . . . . . . . . . .   6
       3.2.2.  Action Fields Format  . . . . . . . . . . . . . . . .   8
     3.3.  Capability Negotiation  . . . . . . . . . . . . . . . . .   9
   4.  Applications  . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.1.  Outbound Traffic Control  . . . . . . . . . . . . . . . .   9
     4.2.  Inbound Traffic Control . . . . . . . . . . . . . . . . .  12
   5.  Additional Contributors . . . . . . . . . . . . . . . . . . .  14
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   On a traditional IP network, devices calculate their respective paths
   in a dynamic and distributed manner.  The entire network is divided
   into multiple autonomous systems (ASs), and an Interior Gateway
   Protocol (IGP) runs on the devices within each AS.  The IGP enables
   devices within an AS to obtain the intra-AS network topology and use
   the same algorithm to calculate routes.  Devices in different ASs use
   Border Gateway Protocol (BGP) to exchange routes.  If a link or
   device fails, the IP network layer triggers route convergence to

Li, et al.               Expires January 7, 2016                [Page 2]
Internet-Draft                 BGP FS RPD                      July 2015
Show full document text