References from RFC 2798
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 1274 | The COSINE and Internet X.500 Schema References Referenced by | Proposed Standard | Possible Reference | |
| RFC 1847 | Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted References Referenced by | Proposed Standard | Possible Reference | |
| RFC 2068 | Hypertext Transfer Protocol -- HTTP/1.1 References Referenced by | Proposed Standard | Possible Reference | |
| RFC 2079 | Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs) References Referenced by | Proposed Standard | Possible Reference | |
| RFC 2251 | Lightweight Directory Access Protocol (v3) References Referenced by | Proposed Standard | Possible Reference | |
| RFC 2252 | Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions References Referenced by | Proposed Standard | Possible Reference | |
| RFC 2256 | A Summary of the X.500(96) User Schema for use with LDAPv3 References Referenced by | Proposed Standard | Possible Reference | |
| RFC 2315 | PKCS #7: Cryptographic Message Syntax Version 1.5 References Referenced by | Informational | Possible Reference | |
| RFC 2633 | S/MIME Version 3 Message Specification References Referenced by | Proposed Standard | Possible Reference |