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) | |
---|---|---|---|
Authors | Mohamed Boucadair , Tirumaleswar Reddy.K , Prashanth Patil | ||
Last updated | 2018-11-30 (Latest revision 2018-10-07) | ||
Replaces | draft-boucadair-dots-dhcp | ||
Replaced by | RFC 8973 | ||
Stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
Stream | WG state | Call For Adoption By WG Issued | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-dots-server-discovery | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
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
Tirumaleswar Reddy.K
Prashanth Patil
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)