References from RFC 2048
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 |
|---|---|---|---|---|
| RFC 1049 |
Content-type header field for Internet messages
References Referenced by |
Historic | Possible Reference | |
| RFC 1543 |
Instructions to RFC Authors
References Referenced by |
Informational | Possible Reference | Possible Downref |
| RFC 1602 |
The Internet Standards Process -- Revision 2
References Referenced by |
Informational | Possible Reference | Possible Downref |
| RFC 1700 |
Assigned Numbers
References Referenced by |
Historic | Possible Reference | |
| RFC 2045 |
Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
References Referenced by |
Draft Standard | Possible Reference | |
| RFC 2046 |
Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
References Referenced by |
Draft Standard | Possible Reference | |
| RFC 2049 |
Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples
References Referenced by |
Draft Standard | Possible Reference | |
| RFC 822 |
STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
References Referenced by |
Internet Standard | Possible Reference | |
| RFC 934 |
Proposed standard for message encapsulation
References Referenced by |
Unknown | Possible Reference | Possible Downref |
| STD 11 |
References Referenced by |
Possible Reference |