Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel
draft-reddy-dots-signal-channel-10
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2017-03-28 | ||
| Replaces | draft-reddy-dots-transport | ||
| Replaced by | draft-ietf-dots-signal-channel | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Yang Validation | ☯ 0 errors, 0 warnings. | ||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-dots-signal-channel | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-reddy-dots-signal-channel-10.txt
Abstract
This document specifies the DOTS signal channel, a protocol for signaling the need for protection against Distributed Denial-of- Service (DDoS) attacks to a server capable of enabling network traffic mitigation on behalf of the requesting client. A companion document defines the DOTS data channel, a separate reliable communication layer for DOTS management and configuration.
Authors
Reddy K
(tireddy@cisco.com)
Mohamed Boucadair
(mohamed.boucadair@orange.com)
Prashanth Patil
(praspati@cisco.com)
Andrew Mortensen
(amortensen@arbor.net)
Nik Teague
(nteague@verisign.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)