Flowspec Clarification
draft-loibl-bacher-idr-flowspec-clarification-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Christoph Loibl , Martin Bacher | ||
| Last updated | 2017-02-23 (Latest revision 2016-08-22) | ||
| Replaced by | draft-hr-idr-rfc5575bis | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-hr-idr-rfc5575bis | |
| 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 clarifies multiple aspects of Flowspec (RFC 5575) to allow a consistent and robust implementation in an multi vendor / inter provider environment. This document updates RFC 5575.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)