Message Authorizing Email Header Field and its use for Draft & Release
draft-melnikov-mmhs-authorizing-users-10

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-01-22
Stream ISE
Intended RFC status Informational
Formats plain text pdf html bibtex
IETF conflict review conflict-review-melnikov-mmhs-authorizing-users
Stream ISE state Finding Reviewers
Consensus Boilerplate Unknown
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        A. Melnikov
Internet-Draft                                                 Isode Ltd
Intended status: Informational                          January 22, 2016
Expires: July 25, 2016

 Message Authorizing Email Header Field and its use for Draft & Release
                draft-melnikov-mmhs-authorizing-users-10

Abstract

   This document describes a procedure for when an 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 review signatures.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 25, 2016.

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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Melnikov                  Expires July 25, 2016                 [Page 1]
Internet-Draft      Message Authorizing Header Field        January 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

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 MSA . . . . . .   3
     3.3.  Review by Authorizing User(s) . . . . . . . . . . . . . .   4
       3.3.1.  Processing of Encrypted Messages  . . . . . . . . . .   5
       3.3.2.  Authorizing S/MIME signatures . . . . . . . . . . . .   5
     3.4.  Role of other Messaging Agents at the sender's domain . .   5
       3.4.1.  MDA at the sender's domain  . . . . . . . . . . . . .   5
       3.4.2.  Border MTA at the sender's domain . . . . . . . . . .   6
   4.  MMHS-Authorizing-Users header field . . . . . . . . . . . . .   6
   5.  Updated MIXER mapping . . . . . . . . . . . . . . . . . . . .   6
     5.1.  Mapping from RFC 5322/MIME to X.400 . . . . . . . . . . .   6
     5.2.  Mapping from X.400 to RFC 5322/MIME . . . . . . . . . . .   7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
     7.1.  Forged Header Fields  . . . . . . . . . . . . . . . . . .   8
     7.2.  Intentionally Malformed Header Fields . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  10
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   In some secure environments email messages can't be released to the
   MTS (Message Transfer System) and, thus 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 DKIM [RFC6376].

   This document describes a procedure for how an email message composed
   by one user can be released to the MTS when one or more authorizing
   users authorize and optionally countersign the message.  The MMHS-
   Authorizing-Users header field (see Section 4) communicates which
   user(s) authorized the message.  If S/MIME signed, the resulting
Show full document text