References from draft-cui-anti-ddos-problem-statement
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.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8612 |
DDoS Open Threat Signaling (DOTS) Requirements
References Referenced by |
Informational | normatively references | |
| RFC 8782 |
Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8811 |
DDoS Open Threat Signaling (DOTS) Architecture
References Referenced by |
Informational | normatively references | |
| RFC 8816 |
Secure Telephone Identity Revisited (STIR) Out-of-Band Architecture and Use Cases
References Referenced by |
Informational | normatively references | |
| RFC 8903 |
Use Cases for DDoS Open Threat Signaling
References Referenced by |
Informational | normatively references | |
| RFC 9005 |
Path Computation Element Communication Protocol (PCEP) Extension for Associating Policies and Label Switched Paths (LSPs)
References Referenced by |
Proposed Standard | normatively references |