RFC 7508: Securing Header Fields with S/MIME

This document describes how the S/MIME protocol can be extended in order to secure message header fields defined in RFC 5322. This technology provides…

Read RFC 7508 on the RFC Editor

Outgoing relationships (15 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5652: Cryptographic Message Syntax (CMS)
Normative reference — RFC 5322: Internet Message Format
Normative reference — RFC 2634: Enhanced Security Services for S/MIME
Normative reference — RFC 6376: DomainKeys Identified Mail (DKIM) Signatures
Normative reference — RFC 4853: Cryptographic Message Syntax (CMS) Multiple Signer Clarification
Informative reference — RFC 3501: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
Informative reference — RFC 5321: Simple Mail Transfer Protocol
Informative reference — RFC 5751: Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification
Informative reference — RFC 3207: SMTP Service Extension for Secure SMTP over Transport Layer Security
Informative reference — RFC 5598: Internet Mail Architecture
Informative reference — RFC 2595: Using TLS with IMAP, POP3 and ACAP
Informative reference — RFC 6532: Internationalized Email Headers
Informative reference — RFC 5750: Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate Handling
Informative reference — RFC 3183: Domain Security Services using S/MIME