References from draft-abarth-thewebsocketprotocol
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 90 |
References Referenced by |
normatively references | ||
| draft-abarth-origin |
The Web Origin Concept
References Referenced by |
normatively references | ||
| draft-ietf-httpstate-cookie |
HTTP State Management Mechanism
References Referenced by |
Proposed Standard | Possible Reference | |
| draft-ietf-websec-origin |
The Web Origin Concept
References Referenced by |
Proposed Standard | Possible Reference | |
| RFC 1951 |
DEFLATE Compressed Data Format Specification version 1.3
References Referenced by |
Informational | normatively references | |
| RFC 2109 |
HTTP State Management Mechanism
References Referenced by |
Historic | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2246 |
The TLS Protocol Version 1.0
References Referenced by |
Historic | normatively references | |
| RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | normatively references | |
| RFC 2965 |
HTTP State Management Mechanism
References Referenced by |
Historic | normatively references | |
| RFC 3490 |
Internationalizing Domain Names in Applications (IDNA)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3548 |
The Base16, Base32, and Base64 Data Encodings
References Referenced by |
Informational | normatively references | |
| RFC 3629 |
UTF-8, a transformation format of ISO 10646
References Referenced by |
Internet Standard | normatively references | |
| RFC 3864 |
Registration Procedures for Message Header Fields
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
| RFC 3987 |
Internationalized Resource Identifiers (IRIs)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 4366 |
Transport Layer Security (TLS) Extensions
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Internet Standard | normatively references | |
| STD 63 |
References Referenced by |
normatively references | ||
| STD 66 |
References Referenced by |
normatively references | ||
| STD 68 |
References Referenced by |
normatively references |