References from draft-h-dots-mitigation-offload-expansion
This is an experimental product. 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 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
draft-ietf-dots-requirements |
DDoS Open Threat Signaling (DOTS) Requirements Refs Ref'd by |
Informational | informatively references | |
draft-ietf-dots-signal-channel |
Distributed Denial-of-Service
Open Threat Signaling (DOTS) Signal Channel Specification Refs Ref'd by |
Proposed Standard | informatively references | |
draft-ietf-dots-use-cases |
Use cases for DDoS Open Threat Signaling Refs Ref'd by |
Informational | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
RFC 4271 |
A Border Gateway Protocol 4 (BGP-4) Refs Ref'd by |
Draft Standard | normatively references | |
RFC 5575 |
Dissemination of Flow Specification Rules Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 7049 |
Concise Binary Object Representation (CBOR) Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 7950 |
The YANG 1.1 Data Modeling Language Refs Ref'd by |
Proposed Standard | normatively references |