References to draft-ietf-dots-use-cases

These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.

Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.

Document	Title	Status	Type	Downref
draft-cui-anti-ddos-problem-statement As rfc8903	Problem Statement:Collaborative Defense of DDoS Attacks References Referenced by		normatively references
RFC 8404	Effects of Pervasive Encryption on Operators References Referenced by	Informational	informatively references
RFC 8612	DDoS Open Threat Signaling (DOTS) Requirements References Referenced by	Informational	informatively references
RFC 8782	Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification References Referenced by	Proposed Standard	informatively references
RFC 8811	DDoS Open Threat Signaling (DOTS) Architecture References Referenced by	Informational	informatively references
RFC 8973	DDoS Open Threat Signaling (DOTS) Agent Discovery References Referenced by	Proposed Standard	informatively references
RFC 9066	Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Call Home References Referenced by	Proposed Standard	informatively references
RFC 9132 As rfc8903	Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification References Referenced by	Proposed Standard	informatively references
RFC 9244 As rfc8903	Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry References Referenced by	Proposed Standard	informatively references
RFC 9284 As rfc8903	Multihoming Deployment Considerations for DDoS Open Threat Signaling (DOTS) References Referenced by	Informational	informatively references
RFC 9387 As rfc8903	Use Cases for DDoS Open Threat Signaling (DOTS) Telemetry References Referenced by	Informational	informatively references