DDoS Mitigation Offload: DOTS Applicability and Deployment Considerations
draft-hayashi-dots-dms-offload-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yuhei Hayashi , Kaname Nishizuka , Mohamed Boucadair | ||
| Last updated | 2020-01-22 (Latest revision 2019-07-21) | ||
| Replaces | draft-hayashi-dots-dms-offload-usecase | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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 describes a deployment scenario to assess the applicability of DOTS protocols together with a discussion on DOTS deployment considerations of such scenario. This scenario assumes that a DMS (DDoS Mitigation System) whose utilization rate is high sends its blocked traffic information to an orchestrator using DOTS protocols, then the orchestrator requests forwarding nodes such as routers to filter the traffic. Doing so enables service providers to mitigate the DDoS attack traffic automatically while ensuring interoperability and distributed filter enforcement.
Authors
Yuhei Hayashi
Kaname Nishizuka
Mohamed Boucadair
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)