%% You should probably cite draft-ietf-lamps-header-protection-requirements-01 instead of this revision. @techreport{ietf-lamps-header-protection-requirements-00, number = {draft-ietf-lamps-header-protection-requirements-00}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-lamps-header-protection-requirements/00/}, author = {Alexey Melnikov and Bernie Hoeneisen}, title = {{Problem Statement and Requirements for Header Protection}}, pagetotal = 20, year = 2019, month = jul, day = 8, abstract = {Privacy and security issues with email header protection in S/MIME have been identified for some time. However, the desire to fix these issue has been expressed in the IETF LAMPS Working Group only recently. The existing S/MIME specification is likely to be updated regarding header protection. Several LAMPS WG participants expressed the opinion that whatever mechanism will be chosen, it should not be limited to S/MIME, but also applicable to PGP/MIME. This document describes the problem statement, generic use cases, and requirements. Additionally it drafts possible solutions to address the challenge. Finally some best practices are collected.}, }