RFC 8612: DDoS Open Threat Signaling (DOTS) Requirements
In plain English — editorial summary, not part of the RFC
This document defines the requirements for the Distributed Denial-of- Service (DDoS) Open Threat Signaling (DOTS) protocols enabling coordinated response to DDoS attacks.
Document record
- Document ID
- RFC8612
- Published
- May 2019
- Authors
- A. Mortensen; T. Reddy; R. Moskowitz
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 22
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8600Using Extensible Messaging and Presence Protocol (XMPP) for Security Information ExchangeCurrent
June 2019
- RFC 8598Split DNS Configuration for the Internet Key Exchange Protocol Version 2 (IKEv2)Current
May 2019
- RFC 8628OAuth 2.0 Device Authorization GrantCurrent
August 2019
- RFC 8636Public Key Cryptography for Initial Authentication in Kerberos (PKINIT) Algorithm AgilityCurrent
July 2019
- RFC 8649Hash Of Root Key Certificate ExtensionCurrent
August 2019
- RFC 8657Certification Authority Authorization (CAA) Record Extensions for Account URI and Automatic Certificate Management Environment (ACME) Method BindingCurrent
November 2019
- RFC 8659DNS Certification Authority Authorization (CAA) Resource RecordCurrent
November 2019
- RFC 8559Dynamic Authorization Proxying in the Remote Authentication Dial-In User Service (RADIUS) ProtocolCurrent
April 2019
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?