References from RFC 2047
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 1522 |
MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text
References Referenced by |
Draft Standard | 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 2048 |
Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
References Referenced by |
Best Current Practice | Reference | |
| RFC 2049 |
Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples
References Referenced by |
Draft Standard | Reference | |
| RFC 822 |
STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
References Referenced by |
Internet Standard | Reference | |
| RFC 934 |
Proposed standard for message encapsulation
References Referenced by |
Unknown | Possible Reference | Possible Downref |
| STD 11 |
References Referenced by |
Reference |