References from RFC 1922
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 1036 |
Standard for interchange of USENET messages
References Referenced by |
Unknown | Reference | |
RFC 1468 |
Japanese Character Encoding for Internet Messages
References Referenced by |
Informational | Reference | |
RFC 1502 |
X.400 Use of Extended Character Sets
References Referenced by |
Historic | Possible 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 1522 |
MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text
References Referenced by |
Draft Standard | Reference | |
RFC 1557 |
Korean Character Encoding for Internet Messages
References Referenced by |
Informational | Reference | |
RFC 1641 |
Using Unicode with MIME
References Referenced by |
Experimental | Reference | |
RFC 1642 |
UTF-7 - A Mail-Safe Transformation Format of Unicode
References Referenced by |
Experimental | Reference | |
RFC 1651 |
SMTP Service Extensions
References Referenced by |
Draft Standard | Reference | |
RFC 1700 |
Assigned Numbers
References Referenced by |
Historic | Reference | |
RFC 1866 |
Hypertext Markup Language - 2.0
References Referenced by |
Historic | Possible Reference | |
RFC 822 |
STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
References Referenced by |
Internet Standard | Reference | |
RFC 854 |
Telnet Protocol Specification
References Referenced by |
Internet Standard | Reference | |
STD 10 |
References Referenced by |
Reference | ||
STD 11 |
References Referenced by |
Reference |