References from draft-ietf-i2nsf-capability
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-i2nsf-terminology |
Interface to Network Security Functions (I2NSF) Terminology
References Referenced by |
informatively references | ||
| draft-ietf-supa-generic-policy-info-model |
Generic Policy Information Model for Simplified Use of Policy Abstractions (SUPA)
References Referenced by |
informatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3198 |
Terminology for Policy-Based Management
References Referenced by |
Informational | normatively references | Downref |
| RFC 5511 |
Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications
References Referenced by |
Proposed Standard | normatively references | |
| RFC 6020 |
YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8192 |
Interface to Network Security Functions (I2NSF): Problem Statement and Use Cases
References Referenced by |
Informational | normatively references | Downref |
| RFC 8329 |
Framework for Interface to Network Security Functions
References Referenced by |
Informational | normatively references | Downref |