References from draft-ietf-dots-signal-filter-control
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 | ||
BCP 215 |
References Referenced by |
informatively references | ||
draft-ietf-dots-architecture |
DDoS Open Threat Signaling (DOTS) Architecture
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 3688 |
The IETF XML Registry
References Referenced by |
Best Current Practice | normatively references | |
RFC 7950 |
The YANG 1.1 Data Modeling Language
References Referenced by |
Proposed Standard | normatively references | |
RFC 7951 |
JSON Encoding of Data Modeled with YANG
References Referenced by |
Proposed Standard | informatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 8340 |
YANG Tree Diagrams
References Referenced by |
Best Current Practice | 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 | normatively references | |
RFC 8783 |
Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel Specification
References Referenced by |
Proposed Standard | normatively references |