Network Working Group A. Melnikov Internet-Draft Isode Ltd Intended status: Informational February 14, 2013 Expires: August 18, 2013 Military Message Handling System (MMHS) over SMTP draft-melnikov-mmhs-profile-02 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 August 18, 2013. Copyright Notice Copyright (c) 2013 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 August 18, 2013 [Page 1] Internet-Draft MMHS over SMTP February 2013 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 . . . . . . . . . . . . 4 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 . . . . . . . . . . . . . . . . . . . 8 Melnikov Expires August 18, 2013 [Page 2] Internet-Draft MMHS over SMTP February 2013 1. Introduction A Military 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] [RFC2049]. [[Maybe be a bit more specific about what is required?]] 3. Parsing, processing and having the ability to generate MMHS header fields [RFC6477]. 4. The ability to insert MT-Priority header field [RFC6758]. 5. Parsing and processing of Multipart/Report Content Type for the Reporting of Mail System Administrative Messages [RFC6522] containing message/delivery-status [RFC3464] and Message Disposition Notification (MDN) [RFC3798]. 6. The ability to request an MDN and the ability to generate an MDN in response to a request [RFC3798]. 7. The ability to send and receive signed and encrypted S/MIME messages [RFC5652] [RFC5751]. 8. The ability to send and receive ESS Security Labels [RFC2634]. MUA can also take advantage of SMTP extensions advertised by MSAs (see Section 4). Melnikov Expires August 18, 2013 [Page 3] Internet-Draft MMHS over SMTP February 2013 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]. 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. The MSA MUST be able to handle the MT- Priority header field as specified in [RFC6758]. 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]. 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]. Melnikov Expires August 18, 2013 [Page 4] Internet-Draft MMHS over SMTP February 2013 3. SMTP extension for Message Transfer Priorities [RFC6710]. "STANAG4406" Priority Assignment Policy MUST be advertised in the EHLO response. The MTA MUST be able to handle the MT-Priority header field as specified in [RFC6758]. 4. SMTP extension for for Delivery Status Notifications [RFC3461]. 5. SMTP Extension for 8-bit MIME transport [RFC6152]. 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 SHOULD be supported in MTAs compliant with this specification: 1. 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. Melnikov Expires August 18, 2013 [Page 5] Internet-Draft MMHS over SMTP February 2013 [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. [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. [RFC6758] Melnikov, A. and K. Carlberg, "Tunneling of SMTP Message Transfer Priorities", RFC 6758, October 2012. [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996. Melnikov Expires August 18, 2013 [Page 6] Internet-Draft MMHS over SMTP February 2013 [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. [RFC2049] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples", RFC 2049, November 1996. [RFC2634] Hoffman, P., "Enhanced Security Services for S/MIME", RFC 2634, June 1999. [RFC5652] Housley, R., "Cryptographic Message Syntax (CMS)", STD 70, RFC 5652, September 2009. [RFC5751] Ramsdell, B. and S. Turner, "Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification", RFC 5751, January 2010. [RFC3464] Moore, K. and G. Vaudreuil, "An Extensible Message Format for Delivery Status Notifications", RFC 3464, January 2003. [RFC6522] Kucherawy, M., "The Multipart/Report Media Type for the Reporting of Mail System Administrative Messages", STD 73, RFC 6522, January 2012. [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. Melnikov Expires August 18, 2013 [Page 7] Internet-Draft MMHS over SMTP February 2013 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 August 18, 2013 [Page 8]