RFC 6698: The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSA

Encrypted communication on the Internet often uses Transport Layer Security (TLS), which depends on third parties to certify the keys used. This document…

Read RFC 6698 on the RFC Editor

Outgoing relationships (25 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Normative reference — RFC 5280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
Normative reference — RFC 1035: Domain names - implementation and specification
Normative reference — RFC 1034: Domain names - concepts and facilities
Normative reference — RFC 4033: DNS Security Introduction and Requirements
Normative reference — RFC 6347: Datagram Transport Layer Security Version 1.2
Normative reference — RFC 4034: Resource Records for the DNS Security Extensions
Normative reference — RFC 4035: Protocol Modifications for the DNS Security Extensions
Normative reference — 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)
Informative reference — RFC 2818: HTTP Over TLS
Informative reference — RFC 2782: A DNS RR for specifying the location of services (DNS SRV)
Informative reference — RFC 5890: Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework
Informative reference — RFC 6234: US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF)
Informative reference — RFC 6066: Transport Layer Security (TLS) Extensions: Extension Definitions
Informative reference — RFC 952: DoD Internet host table specification
Informative reference — RFC 2845: Secret Key Transaction Authentication for DNS (TSIG)
Informative reference — RFC 6376: DomainKeys Identified Mail (DKIM) Signatures
Informative reference — RFC 2931: DNS Request and Transaction Signatures ( SIG(0)s )
Informative reference — RFC 4025: A Method for Storing IPsec Keying Material in DNS
Informative reference — RFC 4641: DNSSEC Operational Practices
Informative reference — RFC 4255: Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints
Informative reference — RFC 6071: IP Security (IPsec) and Internet Key Exchange (IKE) Document Roadmap
Informative reference — RFC 5074: DNSSEC Lookaside Validation (DLV)
Informative reference — RFC 6394: Use Cases and Requirements for DNS-Based Authentication of Named Entities (DANE)

Incoming relationships (32 related RFCs)

Updated by — RFC 7218: Adding Acronyms to Simplify Conversations about DNS-Based Authentication of Named Entities (DANE)
Updated by, Normatively referenced by — RFC 7671: The DNS-Based Authentication of Named Entities (DANE) Protocol: Updates and Operational Guidance
Updated by, Normatively referenced by — RFC 8749: Moving DNSSEC Lookaside Validation (DLV) to Historic Status
Normatively referenced by — RFC 7435: Opportunistic Security: Some Protection Most of the Time
Normatively referenced by — RFC 6797: HTTP Strict Transport Security (HSTS)
Normatively referenced by — RFC 8310: Usage Profiles for DNS over TLS and DNS over DTLS
Normatively referenced by — RFC 7486: HTTP Origin-Bound Authentication (HOBA)
Normatively referenced by — RFC 7672: SMTP Security via Opportunistic DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS)
Normatively referenced by — RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access
Normatively referenced by — RFC 8659: DNS Certification Authority Authorization (CAA) Resource Record
Normatively referenced by — RFC 6844: DNS Certification Authority Authorization (CAA) Resource Record
Normatively referenced by — RFC 7808: Time Zone Data Distribution Service
Normatively referenced by — RFC 8162: Using Secure DNS to Associate Certificates with Domain Names for S/MIME
Normatively referenced by — RFC 7712: Domain Name Associations (DNA) in the Extensible Messaging and Presence Protocol (XMPP)
Normatively referenced by — RFC 8935: Push-Based Security Event Token (SET) Delivery Using HTTP
Normatively referenced by — RFC 8936: Poll-Based Security Event Token (SET) Delivery Using HTTP
Normatively referenced by — RFC 9102: TLS DNSSEC Chain Extension
Normatively referenced by — RFC 9704: Establishing Local DNS Authority in Validated Split-Horizon Environments
Informatively referenced by — RFC 8126: Guidelines for Writing an IANA Considerations Section in RFCs
Informatively referenced by — RFC 7250: Using Raw Public Keys in Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
Informatively referenced by — RFC 9325: Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
Informatively referenced by — RFC 8224: Authenticated Identity Management in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 6837: NERD: A Not-so-novel Endpoint ID (EID) to Routing Locator (RLOC) Database
Informatively referenced by — RFC 6920: Naming Things with Hashes
Informatively referenced by — RFC 9525: Service Identity in TLS
Informatively referenced by — RFC 7852: Additional Data Related to an Emergency Call
Informatively referenced by — RFC 7305: Report from the IAB Workshop on Internet Technology Adoption and Transition (ITAT)
Informatively referenced by — RFC 9174: Delay-Tolerant Networking TCP Convergence-Layer Protocol Version 4
Informatively referenced by — RFC 7711: PKIX over Secure HTTP (POSH)
Informatively referenced by — RFC 7817: Updated Transport Layer Security (TLS) Server Identity Check Procedure for Email-Related Protocols
Informatively referenced by — RFC 8280: Research into Human Rights Protocol Considerations
Informatively referenced by — RFC 9289: Towards Remote Procedure Call Encryption by Default