RFC 8973: DDoS Open Threat Signaling (DOTS) Agent Discovery
In plain English — editorial summary, not part of the RFC
This document specifies mechanisms to configure DDoS Open Threat Signaling (DOTS) clients with their DOTS servers. The discovery procedure also covers the DOTS signal channel Call Home. It can be useful to know the appropriate DOTS server for a given location in order to engage mitigation actions. This is true even in cases where the DOTS client cannot localize the attack: cases where it only knows that some resources are under attack and that help is needed.
Document record
- Document ID
- RFC8973
- Published
- January 2021
- Authors
- M. Boucadair; T. Reddy.K
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9066Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Call HomeCurrent
December 2021
- RFC 9132Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel SpecificationCurrent
September 2021
- RFC 9133Controlling Filtering Rules Using Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal ChannelCurrent
September 2021
- RFC 8783Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel SpecificationCurrent
May 2020
- RFC 8782Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel SpecificationObsoleted
May 2020
- RFC 9244Distributed Denial-of-Service Open Threat Signaling (DOTS) TelemetryCurrent
June 2022
- RFC 9387Use Cases for DDoS Open Threat Signaling (DOTS) TelemetryCurrent
April 2023
- RFC 9145Integrity Protection for the Network Service Header (NSH) and Encryption of Sensitive Context HeadersCurrent
December 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?