References from draft-nottingham-http-link-header
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 13 |
References Referenced by |
normatively references | ||
| BCP 14 |
References Referenced by |
normatively references | ||
| BCP 26 |
References Referenced by |
normatively references | ||
| BCP 47 |
References Referenced by |
normatively references | ||
| BCP 9 |
References Referenced by |
normatively references | ||
| BCP 90 |
References Referenced by |
normatively references | ||
| RFC 2026 |
The Internet Standards Process -- Revision 3
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2068 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Proposed Standard | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2231 |
MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations
References Referenced by |
Proposed Standard | Possible Reference | |
| RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | normatively references | |
| RFC 2817 |
Upgrading to TLS Within HTTP/1.1
References Referenced by |
Proposed Standard | informatively references | |
| RFC 2818 |
HTTP Over TLS
References Referenced by |
Informational | informatively 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 4287 |
The Atom Syndication Format
References Referenced by |
Proposed Standard | informatively references | |
| RFC 4288 |
Media Type Specifications and Registration Procedures
References Referenced by |
Best Current Practice | normatively references | |
| RFC 4685 |
Atom Threading Extensions
References Referenced by |
Proposed Standard | informatively references | |
| RFC 4946 |
Atom License Extension
References Referenced by |
Experimental | informatively references | |
| RFC 5005 |
Feed Paging and Archiving
References Referenced by |
Proposed Standard | informatively references | |
| RFC 5023 |
The Atom Publishing Protocol
References Referenced by |
Proposed Standard | informatively references | |
| RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
| RFC 5646 |
Tags for Identifying Languages
References Referenced by |
Best Current Practice | normatively references | |
| RFC 5741 |
RFC Streams, Headers, and Boilerplates
References Referenced by |
Informational | Possible Reference | Possible Downref |
| RFC 5829 |
Link Relation Types for Simple Version Navigation between Web Resources
References Referenced by |
Informational | informatively references | |
| RFC 5987 |
Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters
References Referenced by |
Historic | normatively references | |
| STD 66 |
References Referenced by |
normatively references |