References from RFC 3066
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 11 | References Referenced by | Reference | ||
| BCP 14 | References Referenced by | Reference | ||
| BCP 9 | References Referenced by | Reference | ||
| RFC 1327 | Mapping between X.400(1988) / ISO 10021 and RFC 822 References Referenced by | Proposed Standard | Reference | |
| RFC 1521 | MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies References Referenced by | Draft Standard | Reference | |
| RFC 1766 | Tags for the Identification of Languages References Referenced by | Proposed Standard | Reference | |
| RFC 2026 | The Internet Standards Process -- Revision 3 References Referenced by | Best Current Practice | Reference | |
| RFC 2028 | The Organizations Involved in the IETF Standards Process References Referenced by | Best Current Practice | Reference | |
| RFC 2119 | Key words for use in RFCs to Indicate Requirement Levels References Referenced by | Best Current Practice | Reference | |
| RFC 2234 | Augmented BNF for Syntax Specifications: ABNF References Referenced by | Proposed Standard | Reference | |
| RFC 2616 | Hypertext Transfer Protocol -- HTTP/1.1 References Referenced by | Draft Standard | Reference | |
| RFC 2860 | Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority References Referenced by | Informational | Reference | |
| RFC 822 | STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES References Referenced by | Internet Standard | Reference |