RFC 9788: Header Protection for Cryptographically Protected Email

S/MIME version 3.1 introduced a mechanism to provide end-to-end cryptographic protection of email message headers. However, few implementations generate…

Read RFC 9788 on the RFC Editor

Outgoing relationships (27 related RFCs)

Updates, Normative reference — RFC 8551: Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Message Specification
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 5234: Augmented BNF for Syntax Specifications: ABNF
Normative reference — RFC 8126: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
Normative reference — RFC 5652: Cryptographic Message Syntax (CMS)
Normative reference — RFC 5322: Internet Message Format
Normative reference — RFC 3864: Registration Procedures for Message Header Fields
Normative reference — RFC 5083: Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content Type
Normative reference — RFC 9580: OpenPGP
Normative reference — RFC 9787: Guidance on End-to-End Email Security
Informative reference — RFC 1035: Domain names - implementation and specification
Informative reference — RFC 5890: Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework
Informative reference — RFC 2047: MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
Informative reference — RFC 3851: Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification
Informative reference — RFC 5751: Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification
Informative reference — RFC 5891: Internationalized Domain Names in Applications (IDNA): Protocol
Informative reference — RFC 2049: Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples
Informative reference — RFC 6376: DomainKeys Identified Mail (DKIM) Signatures
Informative reference — RFC 3156: MIME Security with OpenPGP
Informative reference — RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC)
Informative reference — RFC 4021: Registration of Mail and MIME Header Fields
Informative reference — RFC 7929: DNS-Based Authentication of Named Entities (DANE) Bindings for OpenPGP
Informative reference — RFC 8162: Using Secure DNS to Associate Certificates with Domain Names for S/MIME
Informative reference — RFC 8617: The Authenticated Received Chain (ARC) Protocol
Informative reference — RFC 9216: S/MIME Example Keys and Certificates

Incoming relationships (1 related RFC)

Normatively referenced by — RFC 9787: Guidance on End-to-End Email Security