The aim of DDoS Open Threat Signaling (DOTS) is to develop a standards based approach for the realtime signaling of DDoS related telemetry and threat handling requests and data between elements concerned with DDoS attack detection, classification, traceback, and mitigation.
The working group authors use the dotswg project in github for working versions of the documents and to track issues. Each document uses a distinct repository.
The following are implementations of DOTS.
| Name | Language | Role | Signal Version | Data Version | Comments/Features/Limitations |
|---|---|---|---|---|---|
| go-dots (NTT) | Go | Client+Server | RFC 9132 | RFC 8783 | |
| NCC Group | Client+Server | RFC 9132 | RFC 8783 | ||
| Arbor Networks | Client | -17 |
If you are an implementer please let the working group know about your work and any issues you've found with the drafts by sending comments to the mailing list.
The following are public test servers for DOTS.
| Name | Supported Versions | Access URL | **Comments/Features/Limitations ** |
|---|---|---|---|
| Proprietary | RFC9132 RFC8783 RFC8768 RFC8973 RFC9066 RFC9133 RFC9177 RFC9244 |
Signal * coaps://dotsserver.jpshallow.com:4646 * coaps+tcp://dotsserver.jpshallow.com:4646 Call-Home * coaps://dotscallhome.jpshallow.com:4647 * coaps+tcp://dotscallhome.jpshallow.com:4647 Data * https://dotsserver.jpshallow.com:443 |
PKI support: Use Client and CA Certificates from Certificates for access Mitigation requests for 1.1.1.69, 1.1.1.71, and 1.1.2.0/24 supported |
The content of this page was last updated on 2022-04-09. It was migrated from the old Trac wiki on 2023-01-24.