References from draft-thomson-http-nice
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-ietf-core-http-mapping |
Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)
References Referenced by |
Proposed Standard | informatively references | |
draft-thomson-webpush-http2 |
Generic Event Delivery Using HTTP Push
References Referenced by |
informatively 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 | normatively references | |
RFC 3864 |
Registration Procedures for Message Header Fields
References Referenced by |
Best Current Practice | normatively references | |
RFC 7230 |
Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
References Referenced by |
Proposed Standard | normatively references | |
RFC 7240 |
Prefer Header for HTTP
References Referenced by |
Proposed Standard | informatively references | |
RFC 7252 |
The Constrained Application Protocol (CoAP)
References Referenced by |
Proposed Standard | informatively references |