References from draft-chen-dots-server-hierarchical-deployment
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 |
---|---|---|---|---|
BCP 14 |
References Referenced by |
normatively references | ||
draft-ietf-dots-architecture |
DDoS Open Threat Signaling (DOTS) Architecture
References Referenced by |
Informational | informatively references | |
draft-ietf-dots-multihoming |
Multihoming Deployment Considerations for DDoS Open Threat Signaling (DOTS)
References Referenced by |
Informational | informatively references | |
draft-ietf-dots-requirements |
DDoS Open Threat Signaling (DOTS) Requirements
References Referenced by |
Informational | informatively references | |
draft-ietf-dots-server-discovery |
DDoS Open Threat Signaling (DOTS) Agent Discovery
References Referenced by |
Proposed Standard | informatively references | |
draft-ietf-dots-signal-call-home |
Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Call Home
References Referenced by |
Proposed Standard | informatively references | |
draft-ietf-dots-signal-channel |
Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
References Referenced by |
Proposed Standard | informatively references | |
draft-ietf-dots-use-cases |
Use Cases for DDoS Open Threat Signaling
References Referenced by |
Informational | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 7950 |
The YANG 1.1 Data Modeling Language
References Referenced by |
Proposed Standard | normatively references |