Military Message Handling System (MMHS) over SMTP
draft-melnikov-mmhs-profile-07
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Alexey Melnikov , Graeme Lunt , Alan Ross | ||
| Last updated | 2015-01-02 (Latest revision 2014-07-01) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 or ACP 123. This document specifies how a comparable messaging service can be provided using Internet Electronic Mail, SMTP and their extensions.
Authors
Alexey Melnikov
Graeme Lunt
Alan Ross
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)