BGP Flow-Spec Redirect-to-IP Action
draft-ietf-idr-flowspec-redirect-ip-16

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-idr-flowspec-redirect-ip@ietf.org, idr-chairs@ietf.org, idr@ietf.org, ketant.ietf@gmail.com, rfc-editor@rfc-editor.org, shares@ndzh.com
Subject: Protocol Action: 'BGP Flow-Spec Redirect-to-IP Action' to Proposed Standard (draft-ietf-idr-flowspec-redirect-ip-16.txt)

The IESG has approved the following document:
- 'BGP Flow-Spec Redirect-to-IP Action'
  (draft-ietf-idr-flowspec-redirect-ip-16.txt) as Proposed Standard

This document is the product of the Inter-Domain Routing Working Group.

The IESG contact persons are Gunter Van de Velde, Jim Guichard and Ketan
Talaulikar.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-flowspec-redirect-ip/

Ballot Text

Technical Summary

   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 distributed denial of
   service (DDoS) mitigation.  The flow-spec standard, RFC 8955, defines
   a redirect-to-VRF action for policy-based forwarding.  This mechanism
   can be difficult to use, particularly in networks without L3 VPN
   infrastructure.

   This document defines a new redirect-to-IP flow-spec action that
   provides a simpler method of policy-based forwarding.  The details of
   the action, including the IPv4 or IPv6 target address, are encoded in
   newly defined BGP extended communities.

Working Group Summary

   There was WG consensus with few participants for the WGLC.
   This may be attributed to the fact that the document has
   been around for a long time with multiple implementations
   and deployments. The delay may be attributed to the
   discussions related to FlowSpecv2 which is something that
   the WG was working on in parallel.

Document Quality

   There are multiple implementations of this specification,
   and deployments supporting the maturity of the document.
   There is no other reviews needed by other groups but early
   reviews from various directorates were solicited and the
   comments received were addressed.

Personnel

   The Document Shepherd for this document is Susan Hares. The Responsible
   Area Director is Ketan Talaulikar.

RFC Editor Note