References from draft-ietf-cdni-delegation-acme
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 |
|---|---|---|---|---|
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 7336 |
Framework for Content Distribution Network Interconnection (CDNI)
References Referenced by |
Informational | informatively references | |
| RFC 8006 |
Content Delivery Network Interconnection (CDNI) Metadata
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8008 |
Content Delivery Network Interconnection (CDNI) Request Routing: Footprint and Capabilities Semantics
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 8739 |
Support for Short-Term, Automatically Renewed (STAR) Certificates in the Automated Certificate Management Environment (ACME)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9115 |
An Automatic Certificate Management Environment (ACME) Profile for Generating Delegated Certificates
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9325 |
Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
References Referenced by |
Best Current Practice | normatively references | |
| RFC 9460 |
Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
References Referenced by |
Proposed Standard | informatively references |