References from STD 98
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 26 |
References Referenced by |
informatively references | ||
draft-ietf-httpbis-messaging |
HTTP/1.1
References Referenced by |
Internet Standard | informatively references | |
draft-ietf-httpbis-semantics |
HTTP Semantics
References Referenced by |
Internet Standard | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | informatively references | |
RFC 5234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Internet Standard | normatively references | |
RFC 5861 |
HTTP Cache-Control Extensions for Stale Content
References Referenced by |
Informational | informatively references | |
RFC 6265 |
HTTP State Management Mechanism
References Referenced by |
Proposed Standard | informatively references | |
RFC 7234 |
Hypertext Transfer Protocol (HTTP/1.1): Caching
References Referenced by |
Proposed Standard | informatively references | |
RFC 7405 |
Case-Sensitive String Support in ABNF
References Referenced by |
Proposed Standard | normatively references | Downref |
RFC 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
STD 68 |
References Referenced by |
normatively references |