Browse Prior Art Database

Message Authorizing Email Header Field and Its Use for the Draft and Release Procedure (RFC7912)

IP.com Disclosure Number: IPCOM000246773D
Original Publication Date: 2016-Jun-01
Included in the Prior Art Database: 2016-Jun-29
Document File: 22 page(s) / 24K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Melnikov: AUTHOR

Abstract

In some secure environments, email messages can't be released to the Message Transfer System (MTS); thus, they can't be delivered to recipients unless they are authorized by one or more Authorizing Users (e.g., Releasing Officers or Release Authorities). This document describes how this mechanism can be realized by an additional Internet Email [RFC5322] header field and optionally protected using S/MIME [RFC5750] [RFC5751] or DomainKeys Identified Mail (DKIM) [RFC6376].

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 11% of the total text.

Independent Submission                                       A. Melnikov Request for Comments: 7912                                     Isode Ltd Category: Informational                                        June 2016 ISSN: 2070-1721

        Message Authorizing Email Header Field and Its Use for the                       Draft and Release Procedure

Abstract

   This document describes a procedure for when a Military Message    Handling System (MMHS) message is composed by one user and is only    released to the mail transfer system when one or more Authorizing    Users authorize release of the message by adding the    MMHS-Authorizing-Users header field.  The resulting message can be    optionally signed by the sender and/or reviewer, allowing recipients    to verify both the original signature (if any) and the review    signatures.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This is a contribution to the RFC Series, independently of any other    RFC stream.  The RFC Editor has chosen to publish this document at    its discretion and makes no statement about its value for    implementation or deployment.  Documents approved for publication by    the RFC Editor are not a candidate for any level of Internet    Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7912.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.

 Melnikov                      Informational                     [Page 1]
 RFC 7912            Message Authorizing Header Field           June 2016

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2

   2.  Conventions Used in This Document . . . . . . . . . . . . . .   3

   3.  Draft and Release Procedure . . . . . . . . . . . . . . . . .   3

     3.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3

     3.2.  Handling of Initial Message Submission by the MSA . . . .   3

     3.3.  Review by Authorizing User(s) . . . . . . . . . . . . . .   4

       3.3.1.  Processing of Encrypted Messages  . . . . . . . . . .   5...