CARVIEW |
Select Language
HTTP/2 200
date: Tue, 07 Oct 2025 07:41:00 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=ILzcz5yY97X3wLSRZmfYFHRpCSMooBabpR8g2Z.v49Q-1759822860-1.0.1.1-uhihfIX4gjlZeNZ1goZzRnELgWv1mYM1JkxwIzahI9YfTu3d2PgfW5pTmWnPdLOqIxFoPaCONZpHb9l2UTi7IJa_jUNa4PLJGRvQUsycxmI; path=/; expires=Tue, 07-Oct-25 08:11:00 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98abc0e6dd531eef-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 8612 » RFC Editor
Search RFCs
RFC 8612
DDoS Open Threat Signaling (DOTS) Requirements, May 2019
- File formats:
- Status:
- INFORMATIONAL
- Authors:
- A. Mortensen
T. Reddy
R. Moskowitz - Stream:
- IETF
- Source:
- dots (sec)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8612
Discuss this RFC: Send questions or comments to the mailing list dots@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8612
Abstract
This document defines the requirements for the Distributed Denial-of- Service (DDoS) Open Threat Signaling (DOTS) protocols enabling coordinated response to DDoS attacks.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us