Skip to main content

DDoS Mitigation Offload Use Case and DOTS Deployment Considerations

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Yuhei Hayashi , Kaname Nishizuka , Mohamed Boucadair
Last updated 2019-07-04
Replaces draft-h-dots-mitigation-offload-expansion
Replaced by draft-hayashi-dots-dms-offload
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-hayashi-dots-dms-offload
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:


This document describes a DDoS mitigation offload use case and DOTS deployment consideration of the use case. This use case 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 DDoS attack traffic automatically while ensuring interoperability and distributed filter enforcement.


Yuhei Hayashi
Kaname Nishizuka
Mohamed Boucadair

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)