Registration of Military Message Handling System (MMHS) Header Fields for Use in Internet Mail
RFC 6477
| Document | Type |
RFC - Informational
(January 2012; No errata)
Was draft-melnikov-mmhs-header-fields (individual in app area)
|
|
|---|---|---|---|
| Authors | Graeme Lunt , Alexey Melnikov | ||
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 6477 (Informational) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Pete Resnick | ||
| Send notices to | BonattiC@ieca.com | ||
Internet Engineering Task Force (IETF) A. Melnikov
Request for Comments: 6477 Isode Ltd
Category: Informational G. Lunt
ISSN: 2070-1721 SMHS Ltd
January 2012
Registration of Military Message Handling System (MMHS)
Header Fields for Use in Internet Mail
Abstract
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 and ACP 123. This document specifies message header fields
and associated processing for RFC 5322 (Internet Message Format) to
provide a comparable messaging service. In addition, this document
provides for a STANAG 4406 / Internet Email Gateway that supports
message conversion.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
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/rfc6477.
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
Melnikov & Lunt Informational [Page 1]
RFC 6477 MMHS Header Fields January 2012
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
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. Registration Templates ..........................................3
3.1. Header Field: MMHS-Exempted-Address ........................5
3.2. Header Field: MMHS-Extended-Authorisation-Info .............5
3.3. Header Field: MMHS-Subject-Indicator-Codes .................6
3.4. Header Field: MMHS-Handling-Instructions ...................6
3.5. Header Field: MMHS-Message-Instructions ....................7
3.6. Header Field: MMHS-Codress-Message-Indicator ...............8
3.7. Header Field: MMHS-Originator-Reference ....................8
3.8. Header Field: MMHS-Primary-Precedence ......................9
3.9. Header Field: MMHS-Copy-Precedence ........................10
3.10. Header Field: MMHS-Message-Type ..........................10
3.11. Header Field: MMHS-Other-Recipients-Indicator-To .........11
3.12. Header Field: MMHS-Other-Recipients-Indicator-CC .........12
3.13. Header Field: MMHS-Acp127-Message-Identifier .............13
3.14. Header Field: MMHS-Originator-PLAD .......................13
4. Formal Syntax ..................................................14
5. Service in Comparison to ACP 123 / STANAG 4406 .................16
6. Gatewaying with ACP 123 / STANAG 4406 ..........................16
7. Gatewaying with ACP 127 ........................................18
8. IANA Considerations ............................................18
9. Security Considerations ........................................18
10. References ....................................................19
10.1. Normative References .....................................19
10.2. Informative References ...................................19
Appendix A. Acknowledgements ......................................21
1. Introduction
[RFC5322] defines a protocol for the format of electronic messages
exchanged on the Internet. MMHS is a military specification defined
in ACP 123 [ACP123] (also specified in STANAG 4406 [STANAG-4406]),
which defines a number of extensions to the basic X.400 (1992)
protocol for the services required by military messaging.
Show full document text