DHCP Options for Distributed-Denial-of-Service Open Threat Signaling (DOTS)
draft-boucadair-dots-dhcp-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mohamed Boucadair | ||
| Last updated | 2017-04-12 | ||
| Replaced by | draft-boucadair-dots-server-discovery | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-boucadair-dots-server-discovery | |
| 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:
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 server that it is under a potential attack so that appropriate mitigation actions are undertaken. This document specifies DHCP (IPv4 and IPv6) options to configure hosts with DOTS servers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)