References from rfc8441
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 | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 6454 |
The Web Origin Concept Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 6455 |
The WebSocket Protocol Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 7230 |
Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 7540 |
Hypertext Transfer Protocol Version 2 (HTTP/2) Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 8164 |
Opportunistic Security for HTTP/2 Refs Ref'd by |
Experimental | normatively references | Downref |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words Refs Ref'd by |
Best Current Practice | normatively references |