Skip to main content

Military Message Handling System (MMHS) over SMTP
draft-melnikov-mmhs-profile-00

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Author Alexey Melnikov
Last updated 2012-08-21
RFC stream (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-melnikov-mmhs-profile-00
Network Working Group                                        A. Melnikov
Internet-Draft                                                 Isode Ltd
Intended status: Informational                           August 21, 2012
Expires: February 22, 2013

           Military Message Handling System (MMHS) over SMTP
                     draft-melnikov-mmhs-profile-00

Abstract

   A Miltary Message Handling System (MMHS) processes formal messages
   ensuring release, distribution, security, and timely delivery across
   national and international strategic and tactical networks.  The MMHS
   Elements of Service are defined as a set of extensions to the ITU-T
   X.400 (1992) international standards and are specified in STANAG 4406
   Edition 2 or ACP 123.  This document specifies how a comparable
   messaging service can be provided using SMTP and its extensions.

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 February 22, 2013.

Copyright Notice

   Copyright (c) 2012 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 February 22, 2013               [Page 1]
Internet-Draft               MMHS over SMTP                  August 2012

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Conventions Used in This Document . . . . . . . . . . . . . . . 3
   3.  Requirements on Mail User Agents  . . . . . . . . . . . . . . . 3
   4.  Requirements on Mail Submission Agents  . . . . . . . . . . . . 3
   5.  Requirements on Mail Transfer Agents  . . . . . . . . . . . . . 4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . . . 5
     8.2.  Informative References  . . . . . . . . . . . . . . . . . . 7
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . . . 7

Melnikov                Expires February 22, 2013               [Page 2]
Internet-Draft               MMHS over SMTP                  August 2012

1.  Introduction

   A Miltary Message Handling System (MMHS) processes formal messages
   ensuring release, distribution, security, and timely delivery across
   national and international strategic and tactical networks.  The MMHS
   Elements of Service are defined as a set of extensions to the ITU-T
   X.400 (1992) international standards and are specified in STANAG 4406
   Edition 2 or ACP 123.  This document specifies how a comparable
   messaging service can be provided using Email Message Format
   [RFC5322], SMTP [RFC5321] and their extensions.

2.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

3.  Requirements on Mail User Agents

   A Mail User Agent (MUA) compliant with this specification MUST
   support

   1.  Internet Message Format [RFC5322].

   2.  Multipurpose Internet Mail Extensions (MIME) [RFC2045] [RFC2046]
       [RFC2047] [RFC4288] [RFC4289] [RFC2049].

   3.  Registration of Military Message Handling System (MMHS) header
       fields for use in Internet Mail [RFC6477].

   Additionally a MUA compliant with this specification MAY support

   1.  The Multipart/Report Content Type for the Reporting of Mail
       System Administrative Messages [RFC3462].

   2.  Message Disposition Notification [RFC3798].

   MUA can also take advantage of SMTP extensions advertised by MSAs
   (see Section 4).

4.  Requirements on Mail Submission Agents

   In addition to the list of requirements specified in [RFC6409], an
   Mail Submission Agent (MSA) compliant with this specification MUST
   support:

   1.   SMTP Extension for Authentication [RFC4954].

Melnikov                Expires February 22, 2013               [Page 3]
Internet-Draft               MMHS over SMTP                  August 2012

   2.   SMTP Extension for Secure SMTP over TLS [RFC3207].

   3.   SMTP Service Extension for Returning Enhanced Error Codes
        [RFC2034].

   4.   Deliver By SMTP Service Extension [RFC2852].

   5.   SMTP extension for Message Transfer Priorities.  [RFC6710]
        "STANAG4406" Priority Assignment Policy MUST be advertised in
        the EHLO response.

   6.   SMTP extension for for Delivery Status Notifications [RFC3461].

   7.   SMTP Extension for 8-bit MIME transport [RFC6152].

   8.   SMTP Extension for Message Size Declaration [RFC1870].

   9.   SMTP Extension for Command Pipelining [RFC2920].

   10.  SMTP Extensions for Transmission of Large and Binary MIME
        Messages [RFC3030].

   The following SMTP extensions are OPTIONAL to support in MSAs
   compliant with this specification:

   1.  SMTP Submission Service Extension for Future Message Release
       [RFC4865].

   2.  SMTP extension for Alternate Recipient Delivery Option.

5.  Requirements on Mail Transfer Agents

   A Mail Transfer Agent (MTA) compliant with this specification MUST
   support

   1.  SMTP Service Extension for Returning Enhanced Error Codes
       [RFC2034].

   2.  Deliver By SMTP Service Extension [RFC2852].

   3.  SMTP extension for Message Transfer Priorities [RFC6710].
       "STANAG4406" Priority Assignment Policy MUST be advertised in the
       EHLO response.

   4.  SMTP extension for for Delivery Status Notifications [RFC3461].

   5.  SMTP Extension for 8-bit MIME transport [RFC6152].

Melnikov                Expires February 22, 2013               [Page 4]
Internet-Draft               MMHS over SMTP                  August 2012

   6.  SMTP Extension for Message Size Declaration [RFC1870].

   7.  SMTP Extension for Command Pipelining [RFC2920].

   8.  SMTP Extensions for Transmission of Large and Binary MIME
       Messages [RFC3030].

   The following SMTP extensions are OPTIONAL to support in MTAs
   compliant with this specification:

   1.  SMTP extension for Alternate Recipient Delivery Option.

   2.  SMTP Extension for Secure SMTP over TLS [RFC3207].

6.  IANA Considerations

   This document doesn't ask for any action from IANA.

7.  Security Considerations

   TBD

8.  References

8.1.  Normative References

   [RFC2033]  Myers, J., "Local Mail Transfer Protocol", RFC 2033,
              October 1996.

   [RFC2034]  Freed, N., "SMTP Service Extension for Returning Enhanced
              Error Codes", RFC 2034, October 1996.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC3461]  Moore, K., "Simple Mail Transfer Protocol (SMTP) Service
              Extension for Delivery Status Notifications (DSNs)",
              RFC 3461, January 2003.

   [RFC5321]  Klensin, J., "Simple Mail Transfer Protocol", RFC 5321,
              October 2008.

   [RFC5322]  Resnick, P., Ed., "Internet Message Format", RFC 5322,
              October 2008.

   [RFC6409]  Gellens, R. and J. Klensin, "Message Submission for Mail",
              STD 72, RFC 6409, November 2011.

Melnikov                Expires February 22, 2013               [Page 5]
Internet-Draft               MMHS over SMTP                  August 2012

   [RFC1870]  Klensin, J., Freed, N., and K. Moore, "SMTP Service
              Extension for Message Size Declaration", STD 10, RFC 1870,
              November 1995.

   [RFC2852]  Newman, D., "Deliver By SMTP Service Extension", RFC 2852,
              June 2000.

   [RFC2920]  Freed, N., "SMTP Service Extension for Command
              Pipelining", STD 60, RFC 2920, September 2000.

   [RFC3030]  Vaudreuil, G., "SMTP Service Extensions for Transmission
              of Large and Binary MIME Messages", RFC 3030,
              December 2000.

   [RFC4865]  White, G. and G. Vaudreuil, "SMTP Submission Service
              Extension for Future Message Release", RFC 4865, May 2007.

   [RFC6152]  Klensin, J., Freed, N., Rose, M., and D. Crocker, "SMTP
              Service Extension for 8-bit MIME Transport", STD 71,
              RFC 6152, March 2011.

   [RFC4954]  Siemborski, R. and A. Melnikov, "SMTP Service Extension
              for Authentication", RFC 4954, July 2007.

   [RFC3207]  Hoffman, P., "SMTP Service Extension for Secure SMTP over
              Transport Layer Security", RFC 3207, February 2002.

   [RFC6477]  Melnikov, A. and G. Lunt, "Registration of Military
              Message Handling System (MMHS) Header Fields for Use in
              Internet Mail", RFC 6477, January 2012.

   [RFC6710]  Melnikov, A. and K. Carlberg, "Simple Mail Transfer
              Protocol Extension for Message Transfer Priorities",
              RFC 6710, August 2012.

   [RFC2045]  Freed, N. and N. Borenstein, "Multipurpose Internet Mail
              Extensions (MIME) Part One: Format of Internet Message
              Bodies", RFC 2045, November 1996.

   [RFC2046]  Freed, N. and N. Borenstein, "Multipurpose Internet Mail
              Extensions (MIME) Part Two: Media Types", RFC 2046,
              November 1996.

   [RFC2047]  Moore, K., "MIME (Multipurpose Internet Mail Extensions)
              Part Three: Message Header Extensions for Non-ASCII Text",
              RFC 2047, November 1996.

   [RFC4288]  Freed, N. and J. Klensin, "Media Type Specifications and

Melnikov                Expires February 22, 2013               [Page 6]
Internet-Draft               MMHS over SMTP                  August 2012

              Registration Procedures", BCP 13, RFC 4288, December 2005.

   [RFC4289]  Freed, N. and J. Klensin, "Multipurpose Internet Mail
              Extensions (MIME) Part Four: Registration Procedures",
              BCP 13, RFC 4289, December 2005.

   [RFC2049]  Freed, N. and N. Borenstein, "Multipurpose Internet Mail
              Extensions (MIME) Part Five: Conformance Criteria and
              Examples", RFC 2049, November 1996.

   [RFC3462]  Vaudreuil, G., "The Multipart/Report Content Type for the
              Reporting of Mail System Administrative Messages",
              RFC 3462, January 2003.

   [RFC3798]  Hansen, T. and G. Vaudreuil, "Message Disposition
              Notification", RFC 3798, May 2004.

8.2.  Informative References

   [RFC5598]  Crocker, D., "Internet Mail Architecture", RFC 5598,
              July 2009.

   [RFC2156]  Kille, S., "MIXER (Mime Internet X.400 Enhanced Relay):
              Mapping between X.400 and RFC 822/MIME", RFC 2156,
              January 1998.

   [RFC6376]  Crocker, D., Hansen, T., and M. Kucherawy, "DomainKeys
              Identified Mail (DKIM) Signatures", RFC 6376,
              September 2011.

Appendix A.  Acknowledgements

   Many thanks for input provided by Steve Kille, Alan Ross, David
   Wilson, Graeme Lunt.

Author's Address

   Alexey Melnikov
   Isode Ltd
   5 Castle Business Village
   36 Station Road
   Hampton, Middlesex  TW12 2BX
   UK

   EMail: Alexey.Melnikov@isode.com

Melnikov                Expires February 22, 2013               [Page 7]