RFC 7281: Authentication-Results Registration for S/MIME Signature Verification
In plain English — editorial summary, not part of the RFC
RFC 7001 specifies the Authentication-Results header field for conveying results of message authentication checks. This document defines a new authentication method to be used in the Authentication- Results header field for S/MIME-related signature checks.
Document record
- Document ID
- RFC7281
- Published
- June 2014
- Authors
- A. Melnikov
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7912Message Authorizing Email Header Field and Its Use for the Draft and Release ProcedureCurrent
June 2016
- RFC 8904DNS Whitelist (DNSWL) Email Authentication Method ExtensionCurrent
September 2020
- RFC 7165Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)Current
April 2014
- RFC 7410A Property Types Registry for the Authentication-Results Header FieldObsoleted
December 2014
- RFC 6211Cryptographic Message Syntax (CMS) Algorithm Identifier Protection AttributeCurrent
April 2011
- RFC 6025ASN.1 TranslationCurrent
October 2010
- RFC 8550Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Certificate HandlingCurrent
April 2019
- RFC 8551Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Message SpecificationUpdated
April 2019
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?