[Idr] I-D Action: draft-vandevelde-idr-flowspec-path-redirect-03.txt
internet-drafts@ietf.org Fri, 08 July 2016 16:08 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B4FC512B02E; Fri, 8 Jul 2016 09:08:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.25.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160708160834.32176.49579.idtracker@ietfa.amsl.com>
Date: Fri, 08 Jul 2016 09:08:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/swMCx3AJwLKuAHiBHD_sXW0d-qs>
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-vandevelde-idr-flowspec-path-redirect-03.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2016 16:08:35 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing of the IETF. Title : Flowspec Indirection-id Redirect Authors : Gunter Van de Velde Wim Henderickx Keyur Patel Arjun Sreekantiah Zhenbin Li Shunwan Zhuang Nan Wu Filename : draft-vandevelde-idr-flowspec-path-redirect-03.txt Pages : 12 Date : 2016-07-08 Abstract: Flowspec 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, particularly if the redirected traffic needs to be steered into an engineered path or into a service plane. This document defines a new extended community known as redirect-to- indirection-id (32-bit) flowspec action to provide advanced redirection capabilities on flowspec clients. When activated, the flowspec extended community is used by a flowspec client to find the correct next-hop entry within a localised indirection-id mapping table. The functionality present in this draft allows a network controller to decouple flowspec functionality from the creation and maintainance of the network's service plane itself including the setup of tunnels and other service constructs that could be managed by other network devices. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-vandevelde-idr-flowspec-path-redirect/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-vandevelde-idr-flowspec-path-redirect-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-vandevelde-idr-flowspec-path-redirect-03 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
- [Idr] I-D Action: draft-vandevelde-idr-flowspec-p… internet-drafts