RFC 9066: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Call Home
In plain English — editorial summary, not part of the RFC
This document specifies the Denial-of-Service Open Threat Signaling (DOTS) signal channel Call Home, which enables a Call Home DOTS server to initiate a secure connection to a Call Home DOTS client and to receive attack traffic information from the Call Home DOTS client. The Call Home DOTS server in turn uses the attack traffic information to identify compromised devices launching outgoing DDoS attacks and take appropriate mitigation action(s). The DOTS signal channel Call Home is not specific to home networks; the solution targets any deployment in which it is required to block DDoS attack traffic closer to the source(s) of a DDoS attack.
Document record
- Document ID
- RFC9066
- Published
- December 2021
- Authors
- T. Reddy.K; M. Boucadair; J. Shallow
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 34
- 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 9133Controlling Filtering Rules Using Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal ChannelCurrent
September 2021
- RFC 8782Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel SpecificationObsoleted
May 2020
- RFC 8783Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel SpecificationCurrent
May 2020
- RFC 8768Constrained Application Protocol (CoAP) Hop-Limit OptionCurrent
March 2020
- RFC 8973DDoS Open Threat Signaling (DOTS) Agent DiscoveryCurrent
January 2021
- RFC 9145Integrity Protection for the Network Service Header (NSH) and Encryption of Sensitive Context HeadersCurrent
December 2021
- RFC 9899Extensions to the YANG Data Model for Access Control Lists (ACLs)Current
December 2025
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?