RFC 9244: Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry
In plain English — editorial summary, not part of the RFC
This document aims to enrich the Distributed Denial-of-Service Open Threat Signaling (DOTS) signal channel protocol with various telemetry attributes, allowing for optimal Distributed Denial-of-Service (DDoS) attack mitigation. It specifies the normal traffic baseline and attack traffic telemetry attributes a DOTS client can convey to its DOTS server in the mitigation request, the mitigation status telemetry attributes a DOTS server can communicate to a DOTS client, and the mitigation efficacy telemetry attributes a DOTS client can communicate to a DOTS server. The telemetry attributes can assist the mitigator in choosing the DDoS mitigation techniques and performing optimal DDoS attack mitigation. This document specifies two YANG modules: one for representing DOTS telemetry message types and one for sharing the attack mapping details over the DOTS data channel.
Document record
- Document ID
- RFC9244
- Published
- June 2022
- Authors
- M. Boucadair; T. Reddy.K; E. Doron; M. Chen; J. Shallow
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 108
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9132Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel SpecificationCurrent
September 2021
- RFC 8782Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel SpecificationObsoleted
May 2020
- RFC 9145Integrity Protection for the Network Service Header (NSH) and Encryption of Sensitive Context HeadersCurrent
December 2021
- RFC 8768Constrained Application Protocol (CoAP) Hop-Limit OptionCurrent
March 2020
- RFC 9387Use Cases for DDoS Open Threat Signaling (DOTS) TelemetryCurrent
April 2023
- RFC 8973DDoS Open Threat Signaling (DOTS) Agent DiscoveryCurrent
January 2021
- RFC 8783Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel SpecificationCurrent
May 2020
- RFC 7767Application-Initiated Check-Pointing via the Port Control Protocol (PCP)Current
February 2016
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?