Distributed-Denial-of-Service Open Threat Signaling (DOTS) Server Discovery
draft-boucadair-dots-server-discovery-05
| Document | Type | Replaced Internet-Draft (candidate for dots WG) | |
|---|---|---|---|
| Last updated | 2018-11-30 (latest revision 2018-10-07) | ||
| Replaces | draft-boucadair-dots-dhcp | ||
| Replaced by | draft-ietf-dots-server-discovery | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-dots-server-discovery | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-boucadair-dots-server-discovery-05.txt
Abstract
It may not be possible for a network to determine the cause for an attack, but instead just realize that some resources seem to be under attack. To fill that gap, Distributed-Denial-of-Service Open Threat Signaling (DOTS) allows a network to inform a DOTS server that it is under a potential attack so that appropriate mitigation actions are undertaken. This document specifies mechanisms to configure nodes with DOTS servers.
Authors
Mohamed Boucadair
(mohamed.boucadair@orange.com)
Reddy K
(tirumaleswarreddy_konda@mcafee.com)
Prashanth Patil
(praspati@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)