References from RFC 2156
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 1026 |
Addendum to RFC 987: (Mapping between X.400 and RFC-822)
References Referenced by |
Unknown | Reference | |
RFC 1137 |
Mapping between full RFC 822 and RFC 822 with restricted encoding
References Referenced by |
Historic | Reference | |
RFC 1138 |
Mapping between X.400(1988) / ISO 10021 and RFC 822
References Referenced by |
Experimental | Reference | |
RFC 1148 |
Mapping between X.400(1988) / ISO 10021 and RFC 822
References Referenced by |
Experimental | Reference | |
RFC 1155 |
Structure and identification of management information for TCP/IP-based internets
References Referenced by |
Internet Standard | Reference | |
RFC 1278 |
A string encoding of Presentation Address
References Referenced by |
Informational | Reference | |
RFC 1327 |
Mapping between X.400(1988) / ISO 10021 and RFC 822
References Referenced by |
Proposed Standard | Reference | |
RFC 1328 |
X.400 1988 to 1984 downgrading
References Referenced by |
Historic | Reference | |
RFC 1484 |
Using the OSI Directory to achieve User Friendly Naming (OSI-DS 24 (v1.2))
References Referenced by |
Historic | Reference | |
RFC 1485 |
A String Representation of Distinguished Names (OSI-DS 23 (v5))
References Referenced by |
Historic | Reference | |
RFC 1494 |
Equivalences between 1988 X.400 and RFC-822 Message Bodies
References Referenced by |
Historic | Possible Reference | |
RFC 1495 |
Mapping between X.400 and RFC-822 Message Bodies
References Referenced by |
Proposed Standard | Reference | |
RFC 1496 |
Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages
References Referenced by |
Historic | Reference | |
RFC 1522 |
MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text
References Referenced by |
Draft Standard | Reference | |
RFC 1766 |
Tags for the Identification of Languages
References Referenced by |
Proposed Standard | Reference | |
RFC 1891 |
SMTP Service Extension for Delivery Status Notifications
References Referenced by |
Proposed Standard | Reference | |
RFC 1894 |
An Extensible Message Format for Delivery Status Notifications
References Referenced by |
Proposed Standard | Reference | |
RFC 2045 |
Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
References Referenced by |
Draft Standard | Reference | |
RFC 2157 |
Mapping between X.400 and RFC-822/MIME Message Bodies
References Referenced by |
Proposed Standard | Reference | |
RFC 2162 |
MaXIM-11 - Mapping between X.400 / Internet mail and Mail-11 mail
References Referenced by |
Experimental | Reference | |
RFC 2163 |
Using the Internet DNS to Distribute MIXER Conformant Global Address Mapping (MCGAM)
References Referenced by |
Proposed Standard | Reference | |
RFC 2164 |
Use of an X.500/LDAP directory to support MIXER address mapping
References Referenced by |
Proposed Standard | Reference | |
RFC 821 |
Simple Mail Transfer Protocol
References Referenced by |
Internet Standard | Reference | |
RFC 822 |
STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
References Referenced by |
Internet Standard | Reference | |
RFC 987 |
Mapping between X.400 and RFC 822
References Referenced by |
Unknown | 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 |