Flowspec Path-id Redirect
draft-vandevelde-idr-flowspec-path-redirect-00

The information below is for an old version of the document
Document Type Active Internet-Draft (idr WG)
Last updated 2016-01-07 (latest revision 2015-09-15)
Replaced by draft-ietf-idr-flowspec-path-redirect
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state Candidate for WG Adoption
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                                        G. Van de Velde
Internet-Draft                                             W. Henderickx
Intended status: Standards Track                          Alcatel-Lucent
Expires: March 17, 2016                                         K. Patel
                                                           Cisco Systems
                                                      September 14, 2015

                       Flowspec Path-id Redirect
             draft-vandevelde-idr-flowspec-path-redirect-00

Abstract

   Flow-spec is an extension to BGP that allows for the dissemination of
   traffic flow specification rules.  This has many possible
   applications but the primary one for many network operators is the
   distribution of traffic filtering actions for DDoS mitigation.  The
   flow-spec standard RFC5575 [2] defines a redirect-to-VRF action for
   policy-based forwarding but this mechanism is not always sufficient,
   particular if the redirected traffic needs to be steered into an
   engineered path.

   This document defines a new redirect-to-Path-id (32-bit or 128-bit)
   flow-spec action to provide advanced redirection capabilities.  When
   activated, the flowspec signalled Path-id is used to identify the
   next-hop redirect information within a localized to the router Path-
   id redirect table.  The Path-id redirect table is a table providing a
   list of Path-id's and router local redirect information.  This allows
   a Flowspec signalled redirect towards a next-hop IP address, next-hop
   local interface or next-hop (traffic engineered) tunnel interface.

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 [1].

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/.

Van de Velde, et al.     Expires March 17, 2016                 [Page 1]
Internet-Draft          Flowspec Path-id Redirect         September 2015

   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 March 17, 2016.

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
   2.  Redirect to Path-id Communities . . . . . . . . . . . . . . .   3
   3.  Redirect using localized Path-id Router Mapping . . . . . . .   4
   4.  Validation Procedures . . . . . . . . . . . . . . . . . . . .   4
   5.  Localized Path-id Table . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Flow-spec RFC5575 [2] is an extension to BGP that allows for the
   dissemination of traffic flow specification rules.  This has many
   possible applications but the primary one for many network operators
   is the distribution of traffic filtering actions for DDoS mitigation.

   Every flow-spec route is effectively a rule, consisting of a matching
   part (encoded in the NLRI field) and an action part (encoded in one
   or more BGP extended community).  The flow-spec standard RFC5575 [2]
   defines widely-used filter actions such as discard and rate limit; it

Van de Velde, et al.     Expires March 17, 2016                 [Page 2]
Show full document text