Co-operative DDoS Mitigation
draft-reddy-dots-transport-06

Document Type Replaced Internet-Draft (individual)
Last updated 2016-08-08
Replaced by draft-reddy-dots-signal-channel
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-reddy-dots-signal-channel
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-reddy-dots-transport-06.txt

Abstract

This document specifies a mechanism that a DOTS client can use to signal that a network is under a Distributed Denial-of-Service (DDoS) attack to an upstream DOTS server so that appropriate mitigation actions are undertaken (including, blackhole, drop, rate-limit, or add to watch list) on the suspect traffic. The document specifies both DOTS signal and data channels. Happy Eyeballs considerations for the DOTS signal channel are also elaborated.

Authors

Tirumaleswar Reddy.K (tireddy@cisco.com)
Dan Wing (dwing@cisco.com)
Prashanth Patil (praspati@cisco.com)
Mike Geller (mgeller@cisco.com)
Mohamed Boucadair (mohamed.boucadair@orange.com)

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