References from draft-ietf-httpbis-proxy-status
This is an experimental product. 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 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| BCP 219 |
DNS Terminology Refs Ref'd by |
Best Current Practice | normatively references | |
| BCP 26 |
Guidelines for Writing an IANA Considerations Section in RFCs Refs Ref'd by |
Best Current Practice | normatively references | |
| draft-ietf-httpbis-cdn-loop |
Loop Detection in Content Delivery Networks (CDNs) Refs Ref'd by |
Proposed Standard | informatively references | |
| draft-ietf-httpbis-header-structure |
Structured Headers for HTTP Refs Ref'd by |
normatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 7301 |
Transport Layer Security (TLS) Application-Layer Protocol Negotiation Extension Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 8499 |
DNS Terminology Refs Ref'd by |
Best Current Practice | normatively references |