References from draft-hares-i2nsf-mgtflow-reqs
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-hares-i2rs-dataflow-req |
I2RS Data Flow Requirements
References Referenced by |
informatively references | ||
| draft-hares-i2rs-protocol-strawman |
I2RS protocol strawman
References Referenced by |
informatively references | ||
| draft-ietf-dots-requirements |
DDoS Open Threat Signaling (DOTS) Requirements
References Referenced by |
Informational | informatively references | |
| draft-ietf-i2nsf-problem-and-use-cases |
Interface to Network Security Functions (I2NSF): Problem Statement and Use Cases
References Referenced by |
Informational | informatively references | |
| draft-ietf-i2rs-architecture |
An Architecture for the Interface to the Routing System
References Referenced by |
Informational | informatively references | |
| draft-ietf-mile-rfc5070-bis |
The Incident Object Description Exchange Format Version 2
References Referenced by |
Proposed Standard | informatively references | |
| draft-ietf-netconf-restconf |
RESTCONF Protocol
References Referenced by |
Proposed Standard | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 5070 |
The Incident Object Description Exchange Format
References Referenced by |
Proposed Standard | informatively references | |
| RFC 6241 |
Network Configuration Protocol (NETCONF)
References Referenced by |
Proposed Standard | informatively references |