References to RFC 6186
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 7672 |
SMTP Security via Opportunistic DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS)
References Referenced by |
Proposed Standard | normatively references | |
RFC 7817 |
Updated Transport Layer Security (TLS) Server Identity Check Procedure for Email-Related Protocols
References Referenced by |
Proposed Standard | normatively references | |
RFC 8553 |
DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names
References Referenced by |
Best Current Practice | normatively references | |
RFC 8620 |
The JSON Meta Application Protocol (JMAP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 9051 |
Internet Message Access Protocol (IMAP) - Version 4rev2
References Referenced by |
Proposed Standard | normatively references | |
RFC 6125 |
Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)
References Referenced by |
Proposed Standard | informatively references | |
RFC 7673 |
Using DNS-Based Authentication of Named Entities (DANE) TLSA Records with SRV Records
References Referenced by |
Proposed Standard | informatively references | |
RFC 8314 |
Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access
References Referenced by |
Proposed Standard | informatively references | |
RFC 9525 |
Service Identity in TLS
References Referenced by |
Proposed Standard | informatively references |