Flowspec Indirection-id Redirect
draft-ietf-idr-flowspec-path-redirect-07
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Gunter Van de Velde , Keyur Patel , Zhenbin Li | ||
| Last updated | 2019-06-16 (Latest revision 2018-12-13) | ||
| Replaces | draft-vandevelde-idr-flowspec-path-redirect | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document defines a new extended community known as "FlowSpec Redirect to indirection-id Extended Community". This extended community triggers advanced redirection capabilities to flowspec clients. When activated, this flowspec extended community is used by a flowspec client to retrieve the corresponding next-hop and encoding information within a localised indirection-id mapping table. The functionality detailed in this document allows a network controller to decouple the BGP flowspec redirection instruction from the operation of the available paths.
Authors
Gunter Van de Velde
Keyur Patel
Zhenbin Li
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)