References from draft-chen-cdni-rr-content-acquisition
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 | ||
BCP 72 |
References Referenced by |
informatively references | ||
draft-ietf-cdni-framework |
Framework for Content Distribution Network Interconnection (CDNI)
References Referenced by |
Informational | Possible Reference | |
draft-ietf-cdni-problem-statement |
Content Distribution Network Interconnection (CDNI) Problem Statement
References Referenced by |
Informational | Possible Reference | |
draft-ietf-cdni-requirements |
Content Distribution Network Interconnection (CDNI) Requirements
References Referenced by |
Informational | Possible Reference | |
draft-ietf-cdni-use-cases |
Use Cases for Content Delivery Network Interconnection
References Referenced by |
Informational | Possible Reference | |
draft-narten-iana-considerations-rfc2434bis |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2629 |
Writing I-Ds and RFCs using XML
References Referenced by |
Informational | informatively references | |
RFC 3552 |
Guidelines for Writing RFC Text on Security Considerations
References Referenced by |
Best Current Practice | informatively references |