RFC 8903: Use Cases for DDoS Open Threat Signaling
In plain English — editorial summary, not part of the RFC
The DDoS Open Threat Signaling (DOTS) effort is intended to provide protocols to facilitate interoperability across disparate DDoS Mitigation solutions. This document presents sample use cases that describe the interactions expected between the DOTS components as well as DOTS messaging exchanges. These use cases are meant to identify the interacting DOTS components, how they collaborate, and what the typical information to be exchanged is.
Document record
- Document ID
- RFC8903
- Published
- May 2021
- Authors
- R. Dobbins; D. Migault; R. Moskowitz; N. Teague; L. Xia; K. Nishizuka
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 13
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8879TLS Certificate CompressionCurrent
December 2020
- RFC 8933Update to the Cryptographic Message Syntax (CMS) for Algorithm Identifier ProtectionCurrent
October 2020
- RFC 8935Push-Based Security Event Token (SET) Delivery Using HTTPCurrent
November 2020
- RFC 8936Poll-Based Security Event Token (SET) Delivery Using HTTPCurrent
November 2020
- RFC 8940Extensible Authentication Protocol (EAP) Session-Id Derivation for EAP Subscriber Identity Module (EAP-SIM), EAP Authentication and Key Agreement (EAP-AKA), and Protected EAP (PEAP)Current
October 2020
- RFC 8951Clarification of Enrollment over Secure Transport (EST): Transfer Encodings and ASN.1Current
November 2020
- RFC 8954Online Certificate Status Protocol (OCSP) Nonce ExtensionObsoleted
November 2020
- RFC 8973DDoS Open Threat Signaling (DOTS) Agent DiscoveryCurrent
January 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?