References from RFC 4027
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 |
|---|---|---|---|---|
| BCP 13 |
References Referenced by |
normatively references | ||
| BCP 78 |
References Referenced by |
informatively references | ||
| RFC 1034 |
Domain names - concepts and facilities
References Referenced by |
Internet Standard | normatively references | |
| RFC 1035 |
Domain names - implementation and specification
References Referenced by |
Internet Standard | Possible Reference | |
| RFC 2048 |
Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2440 |
OpenPGP Message Format
References Referenced by |
Proposed Standard | informatively references | |
| RFC 2535 |
Domain Name System Security Extensions
References Referenced by |
Proposed Standard | informatively references | |
| RFC 2538 |
Storing Certificates in the Domain Name System (DNS)
References Referenced by |
Proposed Standard | informatively references | |
| RFC 2540 |
Detached Domain Name System (DNS) Information
References Referenced by |
Experimental | normatively references | |
| RFC 3597 |
Handling of Unknown DNS Resource Record (RR) Types
References Referenced by |
Proposed Standard | informatively references | |
| RFC 3852 |
Cryptographic Message Syntax (CMS)
References Referenced by |
Proposed Standard | informatively references | |
| STD 13 |
References Referenced by |
normatively references |