References from rfc3529
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 2396 |
Uniform Resource Identifiers (URI): Generic Syntax References Referenced by |
Draft Standard | Reference | |
| RFC 2595 |
Using TLS with IMAP, POP3 and ACAP References Referenced by |
Proposed Standard | Reference | |
| RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1 References Referenced by |
Draft Standard | Reference | |
| RFC 2633 |
S/MIME Version 3 Message Specification References Referenced by |
Proposed Standard | Reference | |
| RFC 2732 |
Format for Literal IPv6 Addresses in URL's References Referenced by |
Proposed Standard | Reference | |
| RFC 2782 |
A DNS RR for specifying the location of services (DNS SRV) References Referenced by |
Proposed Standard | Reference | |
| RFC 3023 |
XML Media Types References Referenced by |
Proposed Standard | Reference | |
| RFC 3080 |
The Blocks Extensible Exchange Protocol Core References Referenced by |
Proposed Standard | Reference | |
| RFC 3156 |
MIME Security with OpenPGP References Referenced by |
Proposed Standard | Reference | |
| RFC 3288 |
Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP) References Referenced by |
Proposed Standard | Reference |