References to RFC 976
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.
Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| RFC 1012 |
Bibliography of Request For Comments 1 through 999
References Referenced by |
Informational | Possible Reference | |
| RFC 1912 |
Common DNS Operational and Configuration Errors
References Referenced by |
Informational | Possible 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 1327 |
Mapping between X.400(1988) / ISO 10021 and RFC 822
References Referenced by |
Proposed Standard | Reference | |
| RFC 1530 |
Principles of Operation for the TPC.INT Subdomain: General Principles and Policy
References Referenced by |
Informational | Reference | |
| RFC 2076 |
Common Internet Message Headers
References Referenced by |
Informational | Reference | |
| RFC 2142 |
Mailbox Names for Common Services, Roles and Functions
References Referenced by |
Proposed Standard | Reference | |
| RFC 987 |
Mapping between X.400 and RFC 822
References Referenced by |
Unknown | Reference |