RFC 8162: Using Secure DNS to Associate Certificates with Domain Names for S/MIME
In plain English — editorial summary, not part of the RFC
This document describes how to use secure DNS to associate an S/MIME user's certificate with the intended domain name, similar to the way that DNS-Based Authentication of Named Entities (DANE), RFC 6698, does for TLS.
Document record
- Document ID
- RFC8162
- Published
- May 2017
- Authors
- P. Hoffman; J. Schlyter
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- sec
- Pages
- 11
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8152CBOR Object Signing and Encryption (COSE)Obsoleted
July 2017
- RFC 8176Authentication Method Reference ValuesCurrent
June 2017
- RFC 8134Management Incident Lightweight Exchange (MILE) Implementation ReportCurrent
May 2017
- RFC 8192Interface to Network Security Functions (I2NSF): Problem Statement and Use CasesCurrent
July 2017
- RFC 8129Authentication Indicator in Kerberos TicketsCurrent
March 2017
- RFC 8121Mutual Authentication Protocol for HTTP: Cryptographic Algorithms Based on the Key Agreement Mechanism 3 (KAM3)Current
April 2017
- RFC 8120Mutual Authentication Protocol for HTTPCurrent
April 2017
- RFC 8103Using ChaCha20-Poly1305 Authenticated Encryption in the Cryptographic Message Syntax (CMS)Current
February 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?