References from draft-opsawg-ipfix-sav
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 |
|---|---|---|---|---|
| draft-ietf-savnet-general-sav-capabilities |
General Source Address Validation Capabilities
References Referenced by |
informatively references | ||
| draft-ietf-savnet-inter-domain-problem-statement |
Gap Analysis, Problem Statement, and Requirements for Inter-Domain SAV
References Referenced by |
informatively references | ||
| draft-li-savnet-sav-yang |
YANG Data Model for Intra-domain and Inter-domain Source Address Validation (SAVNET)
References Referenced by |
normatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 6313 |
Export of Structured Data in IP Flow Information Export (IPFIX)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7011 |
Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information
References Referenced by |
Internet Standard | normatively references | |
| RFC 7012 |
Information Model for IP Flow Information Export (IPFIX)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7013 |
Guidelines for Authors and Reviewers of IP Flow Information Export (IPFIX) Information Elements
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references |