References from draft-hares-i2nsf-capability-data-model
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-hyun-i2nsf-nsf-triggered-steering |
Service Function Chaining-Enabled I2NSF Architecture
References Referenced by |
informatively references | ||
draft-ietf-i2nsf-capability |
Information Model of NSFs Capabilities
References Referenced by |
Proposed Standard | informatively references | |
draft-ietf-i2nsf-terminology |
Interface to Network Security Functions (I2NSF) Terminology
References Referenced by |
informatively references | ||
draft-ietf-i2rs-rib-data-model |
A YANG Data Model for the Routing Information Base (RIB)
References Referenced by |
Proposed Standard | 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 | ||
draft-kim-i2nsf-nsf-facing-interface-data-model |
I2NSF Network Security Functions-Facing Interface YANG Data Model
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 6020 |
YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)
References Referenced by |
Proposed Standard | normatively references | |
RFC 8192 |
Interface to Network Security Functions (I2NSF): Problem Statement and Use Cases
References Referenced by |
Informational | normatively references | |
RFC 8329 |
Framework for Interface to Network Security Functions
References Referenced by |
Informational | normatively references |