Flowspec Indirection-id Redirect
draft-vandevelde-idr-flowspec-path-redirect-01

The information below is for an old version of the document
Document Type Active Internet-Draft (idr WG)
Last updated 2016-01-12
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, Ed.
Internet-Draft                                             W. Henderickx
Intended status: Standards Track                          Alcatel-Lucent
Expires: July 15, 2016                                          K. Patel
                                                           Cisco Systems
                                                        January 12, 2016

                    Flowspec Indirection-id Redirect
             draft-vandevelde-idr-flowspec-path-redirect-01

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 or into a service plane.

   This document defines a new redirect-to-INDIRECTION_ID (32-bit or
   128-bit) flow-spec action to provide advanced redirection
   capabilities.  When activated, the flowspec Indirection-id is used to
   identify the next-hop redirect information within a router locallized
   Indirection-id table.  This allows a flowspec controller to signal
   redirection towards a next-hop IP address, a shortest path tunnel, a
   traffic engineered tunnel or a next-next-hop (traffic engineered)
   tunnel egress 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 July 15, 2016                 [Page 1]
Internet-Draft      Flowspec Indirection-id Redirect        January 2016

   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 July 15, 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
   2.  INDIRECTION_ID and INDIRECTION_ID Table . . . . . . . . . . .   3
   3.  Use Case Scenarios  . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Redirection shortest Path tunnel  . . . . . . . . . . . .   4
     3.2.  Redirection to path-engineered tunnels  . . . . . . . . .   4
     3.3.  Redirection to Next-next-hop tunnels  . . . . . . . . . .   5
   4.  Redirect to INDIRECTION-ID Communities  . . . . . . . . . . .   6
   5.  Redirect using locallized INDIRECTION_ID Router Mapping . . .   6
   6.  Validation Procedures . . . . . . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     10.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

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.

Van de Velde, et al.      Expires July 15, 2016                 [Page 2]
Internet-Draft      Flowspec Indirection-id Redirect        January 2016
Show full document text