References from RFC 2616
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 | Reference | ||
| BCP 18 | References Referenced by | Reference | ||
| BCP 9 | References Referenced by | Reference | ||
| RFC 1036 | Standard for interchange of USENET messages References Referenced by | Unknown | Reference | |
| RFC 1123 | Requirements for Internet Hosts - Application and Support References Referenced by | Internet Standard | Possible Reference | |
| RFC 1305 | Network Time Protocol (Version 3) Specification, Implementation and Analysis References Referenced by | Historic | Reference | |
| RFC 1436 | The Internet Gopher Protocol (a distributed document search and retrieval protocol) References Referenced by | Informational | Reference | |
| RFC 1590 | Media Type Registration Procedure References Referenced by | Informational | Reference | |
| RFC 1630 | Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web References Referenced by | Informational | Reference | |
| RFC 1737 | Functional Requirements for Uniform Resource Names References Referenced by | Informational | Reference | |
| RFC 1738 | Uniform Resource Locators (URL) References Referenced by | Proposed Standard | Reference | |
| RFC 1766 | Tags for the Identification of Languages References Referenced by | Proposed Standard | Reference | |
| RFC 1806 | Communicating Presentation Information in Internet Messages: The Content-Disposition Header References Referenced by | Experimental | Reference | |
| RFC 1808 | Relative Uniform Resource Locators References Referenced by | Proposed Standard | Reference | |
| RFC 1864 | The Content-MD5 Header Field References Referenced by | Draft Standard | Reference | |
| RFC 1866 | Hypertext Markup Language - 2.0 References Referenced by | Historic | Reference | |
| RFC 1867 | Form-based File Upload in HTML References Referenced by | Historic | Reference | |
| RFC 1900 | Renumbering Needs Work References Referenced by | Informational | Reference | |
| RFC 1945 | Hypertext Transfer Protocol -- HTTP/1.0 References Referenced by | Informational | Reference | |
| RFC 1950 | ZLIB Compressed Data Format Specification version 3.3 References Referenced by | Informational | Reference | |
| RFC 1951 | DEFLATE Compressed Data Format Specification version 1.3 References Referenced by | Informational | Reference | |
| RFC 1952 | GZIP file format specification version 4.3 References Referenced by | Informational | Reference | |
| RFC 2026 | The Internet Standards Process -- Revision 3 References Referenced by | Best Current Practice | Reference | |
| RFC 2045 | Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies References Referenced by | Draft Standard | Reference | |
| RFC 2046 | Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types References Referenced by | Draft Standard | Reference | |
| RFC 2047 | MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text References Referenced by | Draft Standard | Reference | |
| RFC 2049 | Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples References Referenced by | Draft Standard | Reference | |
| RFC 2068 | Hypertext Transfer Protocol -- HTTP/1.1 References Referenced by | Proposed Standard | Reference | |
| RFC 2069 | An Extension to HTTP : Digest Access Authentication References Referenced by | Proposed Standard | Reference | |
| RFC 2076 | Common Internet Message Headers References Referenced by | Informational | Reference | |
| RFC 2110 | MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML) References Referenced by | Proposed Standard | Reference | |
| RFC 2119 | Key words for use in RFCs to Indicate Requirement Levels References Referenced by | Best Current Practice | Reference | |
| RFC 2145 | Use and Interpretation of HTTP Version Numbers References Referenced by | Informational | Reference | |
| RFC 2183 | Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field References Referenced by | Proposed Standard | Reference | |
| RFC 2279 | UTF-8, a transformation format of ISO 10646 References Referenced by | Draft Standard | Reference | |
| RFC 2324 | Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0) References Referenced by | Informational | Reference | |
| RFC 2396 | Uniform Resource Identifiers (URI): Generic Syntax References Referenced by | Draft Standard | Reference | |
| RFC 2617 | HTTP Authentication: Basic and Digest Access Authentication References Referenced by | Draft Standard | Reference | |
| RFC 822 | STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES References Referenced by | Internet Standard | Reference | |
| RFC 850 | Standard for interchange of USENET messages References Referenced by | Unknown | Reference | |
| RFC 977 | Network News Transfer Protocol References Referenced by | Proposed Standard | Reference | |
| STD 1 | References Referenced by | Possible Reference | ||
| STD 10 | References Referenced by | Reference | ||
| STD 11 | References Referenced by | Reference | ||
| STD 3 | References Referenced by | Reference | ||
| STD 9 | References Referenced by | Reference |